Dynomotion

Group: DynoMotion Message: 5935 From: zeeschuim Date: 10/31/2012
Subject: torch height control in Mach
Hi
Plasma table on Mach3
I am using a Hypertherm with a torch heigt control unit what give 3 ouputsignals torch on, torch up, torch down, these signals are coupled on the Kanalog JP15 opto input terminals, in mach3 they are in ports & pins inputs: THC on: port2 input pin 13, THC up: port2 input pin 14 and THC down: port2 input pin 15.
So far so good I can see they are working in the Mach3 diagnose screen.
But there is no up and down movement of the Z axe.
Do I need to write something for notifying the Kflop?
thanks,
Cees
Group: DynoMotion Message: 5936 From: Tom Kerekes Date: 10/31/2012
Subject: Re: torch height control in Mach
Hi Cees,

I'm not sure how that is supposed to work in Mach3.  Do know where any information on Mach3 and THC is?

But most likely that was handled by the Mach3 Parallel Port Driver and will need to be replaced by a C Program in KFLOP to watch the up/down signals and jog up and down when it sees the up/down inputs.  You will need to add this into a loop that runs continuously at the end of your Init.c (or whatever yours is called) program.

What isn't clear to me is how you enter and exit the THC mode vs normal Z motion mode.

To be able to move the Z axis independently in KFLOP it must be removed from the coordinated motion system.
DefineCoordSystem(0,1,-1,1);  // Remove Z from the Coordinate System
vs
DefineCoordSystem(0,1,2,-1);  // Keep Z in the Coordinate System
 

Coincidentally someone from the Ukraine just asked me the same question (within the hour) but he is using KMotionCNC.  He came up with:

for(;;)
{
WaitNextTimeSlice();

if (ReadBit(0))                                                             // if plasma is ON?
{
 
if (ReadBit(6))                                                     //Up?
{
Delay_sec(1.0); // Delay for error filter
Jog(2,10000);           // Axis Z move UP
while (!ReadBit(6)) ;
Jog(2,0);      
while (!CheckDone(2))  ;  

}
else if (ReadBit(7))                                     //DOWN?
{
Delay_sec(1.0); //Delay.
Jog(2,-10000);           // Axis Z move DOWN
while (!ReadBit(7)) ;
Jog(2,0);      
while (!CheckDone(2))  ;  

}
}
 
 
Seems to me the delays are excessive and maybe in the wrong place, but it should be a start.
 
Regards
TK
 
Group: DynoMotion Message: 5938 From: zeeschuim Date: 10/31/2012
Subject: Re: torch height control in Mach
Hi Tom

I thought I was ready with your riddles.
On the Mach plasma screen there are a few buttons related with the thc : torch on off; it is the same function as spindle on/off
then a button called THC; it is torch enable toggle with OEM code 123 whatever that means
the next is Reset; with function; Torch Call Zero  with OEM code 124
what have to be done by the THC inputs is the Z up or down according the both inputs in ports & pins
what is happening behind all of this I really don't know!

hellup!!

best regards,
Cees

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> I'm not sure how that is supposed to work in Mach3.  Do know where any information on Mach3 and THC is?
>
> But most likely that was handled by the Mach3 Parallel Port Driver and will need to be replaced by a C Program in KFLOP to watch the up/down signals and jog up and down when it sees the up/down inputs.  You will need to add this into a loop that runs continuously at the end of your Init.c (or whatever yours is called) program.
>
>
> What isn't clear to me is how you enter and exit the THC mode vs normal Z motion mode.
>
> To be able to move the Z axis independently in KFLOP it must be removed from the coordinated motion system.
> DefineCoordSystem(0,1,-1,1);  // Remove Z from the Coordinate System
> vs
> DefineCoordSystem(0,1,2,-1);  // Keep Z in the Coordinate System
>  
>
> Coincidentally someone from the Ukraine just asked me the same question (within the hour) but he is using KMotionCNC.  He came up with:
>
> for(;;)
> {
> WaitNextTimeSlice();
>
> if (ReadBit(0))                                                             // if plasma is ON?
> {
>  if (ReadBit(6))                                                     //Up?
> {
> Delay_sec(1.0);// Delay for error filter
> Jog(2,10000);          // Axis Z move UP
> while (!ReadBit(6)) ;
> Jog(2,0);     
> while (!CheckDone(2))  ;  
>
> }
> else if (ReadBit(7))                                     //DOWN?
> {
> Delay_sec(1.0);//Delay.
> Jog(2,-10000);          // Axis Z move DOWN
> while (!ReadBit(7)) ;
> Jog(2,0);     
> while (!CheckDone(2))  ;  
>
> }
> }
>
>
> Seems to me the delays are excessive and maybe in the wrong place, but it should be a start.
>
> Regards
> TK
>
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Wednesday, October 31, 2012 8:30 AM
> Subject: [DynoMotion] torch height control in Mach
>
>  
> HiPlasma table on Mach3I am using a Hypertherm with a torch heigt control unit what give 3 ouputsignals torch on, torch up, torch down, these signals are coupled on the Kanalog JP15 opto input terminals, in mach3 they are in ports & pins inputs: THC on: port2 input pin 13, THC up: port2 input pin 14 and THC down: port2 input pin 15.So far so good I can see they are working in the Mach3 diagnose screen.But there is no up and down movement of the Z axe.Do I need to write something for notifying the Kflop?thanks,Cees
>
Group: DynoMotion Message: 5940 From: Tom Kerekes Date: 10/31/2012
Subject: Re: torch height control in Mach
Hi Cees,
 
Do you really need to use that Plasma Screen with the buttons that we don't know what they are supposed to do?
 
Regardless, the first step would be develop the Z up/down motion program and get that working.  If you run that program from KMotion while doing a cut does the Z motion up/down happen?  You will of course need to modify it for which Input bits you are wired to.
 
The Port and Pins settings in Mach3 are not really necessary.  I don't think they will do anything in Mach3.  This now has to be handled by KFLOP.
 
You will also have to remove Z from the Coordinate system as I described.  Eventually we will probably want to be able to switch Z modes dependent on Torch ON, or an M Code, or something. 
 
Regards
TK 

Group: DynoMotion Message: 5941 From: zeeschuim Date: 11/1/2012
Subject: Re: torch height control in Mach
Hi Tom

for(;;) what is this?
{
WaitNextTimeSlice(); what is this?

if (ReadBit(0)) // if plasma is ON?
{
if (ReadBit(6)) //Up?
{
Delay_sec(1.0); // Delay for error filter
Jog(2,10000); // Axis Z move UP
while (!ReadBit(6)) ;
Jog(2,0);
while (!CheckDone(2)) ;

}
else if (ReadBit(7)) //DOWN?
{
Delay_sec(1.0); //Delay.
Jog(2,-10000); // Axis Z move DOWN
while (!ReadBit(7)) ;
Jog(2,0);
while (!CheckDone(2)) ;

}
} twice the same } ?

Must I paste this code a C progam and run it? or paste it in another progam with my bits in it?

regards,
Cees

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>  
> Do you really need to use that Plasma Screen with the buttons that we don't know what they are supposed to do?
>  
> Regardless, the first step would be develop the Z up/down motion program and get that working.  If you run that program from KMotion while doing a cut does the Z motion up/down happen?  You will of course need to modify it for which Input bits you are wired to.
>  
> The Port and Pins settings in Mach3 are not really necessary.  I don't think they will do anything in Mach3.  This now has to be handled by KFLOP.
>  
> You will also have to remove Z from the Coordinate system as I described.  Eventually we will probably want to be able to switch Z modes dependent on Torch ON, or an M Code, or something. 
>  
> Regards
> TK 
>
>
> ________________________________
> From: zeeschuim <atmolgers@...>
> To: DynoMotion@yahoogroups.com
> Sent: Wednesday, October 31, 2012 12:13 PM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>  
> Hi Tom
>
> I thought I was ready with your riddles.
> On the Mach plasma screen there are a few buttons related with the thc : torch on off; it is the same function as spindle on/off
> then a button called THC; it is torch enable toggle with OEM code 123 whatever that means
> the next is Reset; with function; Torch Call Zero  with OEM code 124
> what have to be done by the THC inputs is the Z up or down according the both inputs in ports & pins
> what is happening behind all of this I really don't know!
>
> hellup!!
>
> best regards,
> Cees
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:>> Hi Cees,> > I'm not sure how that is supposed to work in Mach3.  Do know where any information on Mach3 and THC is?> > But most likely that was handled by the Mach3 Parallel Port Driver and will need to be replaced by a C Program in KFLOP to watch the up/down signals and jog up and down when it sees the up/down inputs.  You will need to add this into a loop that runs continuously at the end of your Init.c (or whatever yours is called) program.> > > What isn't clear to me is how you enter and exit the THC mode vs normal Z motion mode.> > To be able to move the Z axis independently in KFLOP it must be removed from the coordinated motion system.> DefineCoordSystem(0,1,-1,1);  // Remove Z from the Coordinate System> vs> DefineCoordSystem(0,1,2,-1);  // Keep Z in the Coordinate System>  > > Coincidentally someone from the Ukraine just asked me the same question (within the hour)
> but he is using KMotionCNC.  He came up with:> > for(;;)> {> WaitNextTimeSlice();> > if (ReadBit(0))                                                             // if plasma is ON?> {>  if (ReadBit(6))                                                     //Up?> {> Delay_sec(1.0);// Delay for error filter> Jog(2,10000);          // Axis Z move UP> while (!ReadBit(6)) ; > Jog(2,0);     > while (!CheckDone(2))  ;  > > }> else if (ReadBit(7))                                     //DOWN?> {> Delay_sec(1.0);//Delay.> Jog(2,-10000);          // Axis Z move DOWN> while (!ReadBit(7)) ; > Jog(2,0);     > while (!CheckDone(2))  ;  > > }> }> > > Seems to me the delays are excessive
> and maybe in the wrong place, but it should be a start.> > Regards> TK> > From: zeeschuim atmolgers@> To: DynoMotion@yahoogroups.com > Sent: Wednesday, October 31, 2012 8:30 AM> Subject: [DynoMotion] torch height control in Mach> >   > HiPlasma table on Mach3I am using a Hypertherm with a torch heigt control unit what give 3 ouputsignals torch on, torch up, torch down, these signals are coupled on the Kanalog JP15 opto input terminals, in mach3 they are in ports & pins inputs: THC on: port2 input pin 13, THC up: port2 input pin 14 and THC down: port2 input pin 15.So far so good I can see they are working in the Mach3 diagnose screen.But there is no up and down movement of the Z axe.Do I need to write something for notifying the Kflop?thanks,Cees>
>
Group: DynoMotion Message: 5947 From: Tom Kerekes Date: 11/1/2012
Subject: Re: torch height control in Mach
Hi Cees,
 
The "for" statement in C is one way to loop a section of code over and over.  It is a very powerful statement where you can control how the loop operates.  Between the parenthesis you can put 3 things.  The first is a initializor (something to do before the loop starts), the second is the condition to exit the loop, the third is what happens at the end of each loop.  So for example to do the loop 10 times we might initialize a counter, i, to zero, exit when the count is 10, and count 1 at the end of each loop.  So such a "for" statement might look like:
 
for (i=0; i<10; i++)
{
     // put the stuff to be repeated here
}
 
To loop forever requires no initialization, there is no exit condition, and nothing needs to happen at the end of the loop, so it becomes:
 
for (;;)
{
    // stuff here gets repeated forever
}
 
 
 
Regarding WaitNextTimeSlice() This function waits until the Thread gets its next slice of time which will occur every 180us.  This causes the loop to execute un-interrupted at a nice periodic rate, actually not real crucial for this case.
 
The curly brackets { } in C are very important.  They group statements into a block.  They must always be in matching pairs.  They can be nested (a block within a block).  The very last end bracket pairs with the begin bracket right after the "for" statement.  This defines the end of the instructions that are in the loop.  You might think of them as an abreviated begin/end statement.   Good programmers indent the lines in their programs so it is easy to see all the statements that are in the same block.  But the blasted email system often messes up the indentation.
 
 
Yes this code fragment must be pasted into a program to be able to test it.  It should be all pasted at the end of the "main" function, but inside the "main" function.  The main function's scope is defined by the the begin/end curly brackets.  The begin bracket is right after the "main" declaration.  The end is further down (skipping over any bracket pairs).  So for example:
 
main()
{   // beginning of main function
    // stuff
 
    // stuff
 
    // stuff
 
    // <<<<<<<Paste your Loop here
}  // end of main function
 
HTH
TK
 

Group: DynoMotion Message: 5952 From: zeeschuim Date: 11/2/2012
Subject: Re: torch height control in Mach
Ok Tom

I will do my best to implement it tomorrow.

A Plasma file as example:
X an Y jog to the startpoint of the first contour.
Then there is a G31 macro with the torch to measure the height of the startpoint.
Then the torch goes to pierce heigt say 4mm.
Then there is the M3 command to start the plasma.
Z is going to 1,5mm above the surface
then the THC have to start
Start cutting in X and Y, the torch height 1,5mm above the material is monitored and adjust by the THC.
At the end of the contour THC is of, Z is going to jog height and the torch is off.
the next contour is the same as above.

So the call for the Macro and the start of the torch is in the Gcode, maybee is it possible to implement the THC in the code also??

thanks,
Cees

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>  
> The "for" statement in C is one way to loop a section of code over and over.  It is a very powerful statement where you can control how the loop operates.  Between the parenthesis you can put 3 things.  The first is a initializor (something to do before the loop starts), the second is the condition to exit the loop, the third is what happens at the end of each loop.  So for example to do the loop 10 times we might initialize a counter, i, to zero, exit when the count is 10, and count 1 at the end of each loop.  So such a "for" statement might look like:
>  
> for (i=0; i<10; i++)
> {
>      // put the stuff to be repeated here
> }
>  
> To loop forever requires no initialization, there is no exit condition, and nothing needs to happen at the end of the loop, so it becomes:
>  
> for (;;)
> {
>     // stuff here gets repeated forever
> }
>  
>  
>  
> Regarding WaitNextTimeSlice() This function waits until the Thread gets its next slice of time which will occur every 180us.  This causes the loop to execute un-interrupted at a nice periodic rate, actually not real crucial for this case.
>  
> The curly brackets { } in C are very important.  They group statements into a block.  They must always be in matching pairs.  They can be nested (a block within a block).  The very last end bracket pairs with the begin bracket right after the "for" statement.  This defines the end of the instructions that are in the loop.  You might think of them as an abreviated begin/end statement.   Good programmers indent the lines in their programs so it is easy to see all the statements that are in the same block.  But the blasted email system often messes up the indentation.
>  
>  
> Yes this code fragment must be pasted into a program to be able to test it.  It should be all pasted at the end of the "main" function, but inside the "main" function.  The main function's scope is defined by the the begin/end curly brackets.  The begin bracket is right after the "main" declaration.  The end is further down (skipping over any bracket pairs).  So for example:
>  
> main()
> {   // beginning of main function
>     // stuff
>  
>     // stuff
>  
>     // stuff
>  
>     // <<<<<<<Paste your Loop here
> }  // end of main function
>  
> HTH
> TK
>  
>
>
> ________________________________
> From: zeeschuim <atmolgers@...>
> To: DynoMotion@yahoogroups.com
> Sent: Thursday, November 1, 2012 8:52 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>  
> Hi Tom
>
> for(;;) what is this?
> {
> WaitNextTimeSlice(); what is this?
>
> if (ReadBit(0)) // if plasma is ON?
> {
> if (ReadBit(6)) //Up?
> {
> Delay_sec(1.0); // Delay for error filter
> Jog(2,10000); // Axis Z move UP
> while (!ReadBit(6)) ;
> Jog(2,0);
> while (!CheckDone(2)) ;
>
> }
> else if (ReadBit(7)) //DOWN?
> {
> Delay_sec(1.0); //Delay.
> Jog(2,-10000); // Axis Z move DOWN
> while (!ReadBit(7)) ;
> Jog(2,0);
> while (!CheckDone(2)) ;
>
> }
> } twice the same } ?
>
> Must I paste this code a C progam and run it? or paste it in another progam with my bits in it?
>
> regards,
> Cees
>
> --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Cees,
> >  
> > Do you really need to use that Plasma Screen with the buttons that we don't know what they are supposed to do?
> >  
> > Regardless, the first step would be develop the Z up/down motion program and get that working.  If you run that program from KMotion while doing a cut does the Z motion up/down happen?  You will of course need to modify it for which Input bits you are wired to.
> >  
> > The Port and Pins settings in Mach3 are not really necessary.  I don't think they will do anything in Mach3.  This now has to be handled by KFLOP.
> >  
> > You will also have to remove Z from the Coordinate system as I described.  Eventually we will probably want to be able to switch Z modes dependent on Torch ON, or an M Code, or something. 
> >  
> > Regards
> > TK 
> >
> >
> > ________________________________
> > From: zeeschuim <atmolgers@>
> > To: mailto:DynoMotion%40yahoogroups.com
> > Sent: Wednesday, October 31, 2012 12:13 PM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >  
> > Hi Tom
> >
> > I thought I was ready with your riddles.
> > On the Mach plasma screen there are a few buttons related with the thc : torch on off; it is the same function as spindle on/off
> > then a button called THC; it is torch enable toggle with OEM code 123 whatever that means
> > the next is Reset; with function; Torch Call Zero  with OEM code 124
> > what have to be done by the THC inputs is the Z up or down according the both inputs in ports & pins
> > what is happening behind all of this I really don't know!
> >
> > hellup!!
> >
> > best regards,
> > Cees
> >
> >>
>
Group: DynoMotion Message: 5956 From: zeeschuim Date: 11/4/2012
Subject: Re: torch height control in Mach
Hi Tom

before it goes in THC mode it has to measure the top of the material.
I have tried several macros in Mach3  withtout any luck:(
Is it not possible for you to implement the THC signals in the mach plugin?
best regards,
Cees


--- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@...> wrote:
>
>
>
> Ok Tom
>
> I will do my best to implement it tomorrow.
>
> A Plasma file as example:
> X an Y jog to the startpoint of the first contour.
> Then there is a G31 macro with the torch to measure the height of the startpoint.
> Then the torch goes to pierce heigt say 4mm.
> Then there is the M3 command to start the plasma.
> Z is going to 1,5mm above the surface
> then the THC have to start
> Start cutting in X and Y, the torch height 1,5mm above the material is monitored and adjust by the THC.
> At the end of the contour THC is of, Z is going to jog height and the torch is off.
> the next contour is the same as above.
>
> So the call for the Macro and the start of the torch is in the Gcode, maybee is it possible to implement the THC in the code also??
>
> thanks,
> Cees
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> >
> > Hi Cees,
> >  
> > The "for" statement in C is one way to loop a section of code over and over.  It is a very powerful statement where you can control how the loop operates.  Between the parenthesis you can put 3 things.  The first is a initializor (something to do before the loop starts), the second is the condition to exit the loop, the third is what happens at the end of each loop.  So for example to do the loop 10 times we might initialize a counter, i, to zero, exit when the count is 10, and count 1 at the end of each loop.  So such a "for" statement might look like:
> >  
> > for (i=0; i<10; i++)
> > {
> >      // put the stuff to be repeated here
> > }
> >  
> > To loop forever requires no initialization, there is no exit condition, and nothing needs to happen at the end of the loop, so it becomes:
> >  
> > for (;;)
> > {
> >     // stuff here gets repeated forever
> > }
> >  
> >  
> >  
> > Regarding WaitNextTimeSlice() This function waits until the Thread gets its next slice of time which will occur every 180us.  This causes the loop to execute un-interrupted at a nice periodic rate, actually not real crucial for this case.
> >  
> > The curly brackets { } in C are very important.  They group statements into a block.  They must always be in matching pairs.  They can be nested (a block within a block).  The very last end bracket pairs with the begin bracket right after the "for" statement.  This defines the end of the instructions that are in the loop.  You might think of them as an abreviated begin/end statement.   Good programmers indent the lines in their programs so it is easy to see all the statements that are in the same block.  But the blasted email system often messes up the indentation.
> >  
> >  
> > Yes this code fragment must be pasted into a program to be able to test it.  It should be all pasted at the end of the "main" function, but inside the "main" function.  The main function's scope is defined by the the begin/end curly brackets.  The begin bracket is right after the "main" declaration.  The end is further down (skipping over any bracket pairs).  So for example:
> >  
> > main()
> > {   // beginning of main function
> >     // stuff
> >  
> >     // stuff
> >  
> >     // stuff
> >  
> >     // <<<<<<<Paste your Loop here
> > }  // end of main function
> >  
> > HTH
> > TK
> >  
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Thursday, November 1, 2012 8:52 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >  
> > Hi Tom
> >
> > for(;;) what is this?
> > {
> > WaitNextTimeSlice(); what is this?
> >
> > if (ReadBit(0)) // if plasma is ON?
> > {
> > if (ReadBit(6)) //Up?
> > {
> > Delay_sec(1.0); // Delay for error filter
> > Jog(2,10000); // Axis Z move UP
> > while (!ReadBit(6)) ;
> > Jog(2,0);
> > while (!CheckDone(2)) ;
> >
> > }
> > else if (ReadBit(7)) //DOWN?
> > {
> > Delay_sec(1.0); //Delay.
> > Jog(2,-10000); // Axis Z move DOWN
> > while (!ReadBit(7)) ;
> > Jog(2,0);
> > while (!CheckDone(2)) ;
> >
> > }
> > } twice the same } ?
> >
> > Must I paste this code a C progam and run it? or paste it in another progam with my bits in it?
> >
> > regards,
> > Cees
> >
> > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Cees,
> > >  
> > > Do you really need to use that Plasma Screen with the buttons that we don't know what they are supposed to do?
> > >  
> > > Regardless, the first step would be develop the Z up/down motion program and get that working.  If you run that program from KMotion while doing a cut does the Z motion up/down happen?  You will of course need to modify it for which Input bits you are wired to.
> > >  
> > > The Port and Pins settings in Mach3 are not really necessary.  I don't think they will do anything in Mach3.  This now has to be handled by KFLOP.
> > >  
> > > You will also have to remove Z from the Coordinate system as I described.  Eventually we will probably want to be able to switch Z modes dependent on Torch ON, or an M Code, or something. 
> > >  
> > > Regards
> > > TK 
> > >
> > >
> > > ________________________________
> > > From: zeeschuim <atmolgers@>
> > > To: mailto:DynoMotion%40yahoogroups.com
> > > Sent: Wednesday, October 31, 2012 12:13 PM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >  
> > > Hi Tom
> > >
> > > I thought I was ready with your riddles.
> > > On the Mach plasma screen there are a few buttons related with the thc : torch on off; it is the same function as spindle on/off
> > > then a button called THC; it is torch enable toggle with OEM code 123 whatever that means
> > > the next is Reset; with function; Torch Call Zero  with OEM code 124
> > > what have to be done by the THC inputs is the Z up or down according the both inputs in ports & pins
> > > what is happening behind all of this I really don't know!
> > >
> > > hellup!!
> > >
> > > best regards,
> > > Cees
> > >
> > >>
> >
>
Group: DynoMotion Message: 5957 From: Tom Kerekes Date: 11/4/2012
Subject: Re: torch height control in Mach
Hi Cees,

Probing is something independent of THC.  We should go one step at a time.  G31 probing works well under Mach3 but you must configure the NotifyMach3Probe.c program for your particular probe (how it is wired).  Have you tried this?  Let's get probing working first.  See:

http://dynomotion.com/Help/Mach3Plugin/Mach3Probe.htm

Did you read this?

You should only need to change these two defines in the program.  I assume there is some signal available that indicates when the torch touches the metal?

      #define PROBE_BIT 0
      #define PROBE_ACTIVE_STATE 1


No the Plugin can't do this.  It runs under Windows and would be unreliable.

Regards
TK



Group: DynoMotion Message: 5961 From: zeeschuim Date: 11/5/2012
Subject: Re: torch height control in Mach
Hi Tom

Yes I use that with  bit 139 and DAC_SERVO_MODE.
And now I have made a macro M15 what works for me for every time it goes to another cut  contour.
In the postprocessor from Vcarve I can implement it before every plunge move. (a new cut contour)
So that is done, now the THC??

best regards,
Cees
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> Probing is something independent of THC.  We should go one step at a time.  G31 probing works well under Mach3 but you must configure the NotifyMach3Probe.c program for your particular probe (how it is wired).  Have you tried this?  Let's get probing working first.  See:
>
> http://dynomotion.com/Help/Mach3Plugin/Mach3Probe.htm
>
>
> Did you read this?
>
>
> You should only need to change these two defines in the program.  I assume there is some signal available that indicates when the torch touches the metal?
>
>
>       #define PROBE_BIT 0
>       #define PROBE_ACTIVE_STATE 1
>
>
> No the Plugin can't do this.  It runs under Windows and would be unreliable.
>
> Regards
> TK
>
>
>
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Sunday, November 4, 2012 10:06 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> before it goes in THC mode it has to measure the top of the material.
> I have tried several macros in Mach3  withtout any luck
> Is it not possible for you to implement the THC signals in the mach plugin?
> best regards,
> Cees
>
> --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> >
> >
> >
> > Ok Tom
> >
> > I will do my best to implement it tomorrow.
> >
> > A Plasma file as example:
> > X an Y jog to the startpoint of the first contour.
> > Then there is a G31 macro with the torch to measure the height of the startpoint.
> > Then the torch goes to pierce heigt say 4mm.
> > Then there is the M3 command to start the plasma.
> > Z is going to 1,5mm above the surface
> > then the THC have to start
> > Start cutting in X and Y, the torch height 1,5mm above the material is monitored and adjust by the THC.
> > At the end of the contour THC is of, Z is going to jog height and the torch is off.
> > the next contour is the same as above.
> >
> > So the call for the Macro and the start of the torch is in the Gcode, maybee is it possible to implement the THC in the code also??
> >
> > thanks,
> > Cees
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > >
> > > Hi Cees,
> > >  
> > > The "for" statement in C is one way to loop a section of code over and over.  It is a very powerful statement where you can control how the loop operates.  Between the parenthesis you can put 3 things.  The first is a initializor (something to do before the loop starts), the second is the condition to exit the loop, the third is what happens at the end of each loop.  So for example to do the loop 10 times we might initialize a counter, i, to zero, exit when the count is 10, and count 1 at the end of each loop.  So such a "for" statement might look like:
> > >  
> > > for (i=0; i<10; i++)
> > > {
> > >      // put the stuff to be repeated here
> > > }
> > >  
> > > To loop forever requires no initialization, there is no exit condition, and nothing needs to happen at the end of the loop, so it becomes:
> > >  
> > > for (;;)
> > > {
> > >     // stuff here gets repeated forever
> > > }
> > >  
> > >  
> > >  
> > > Regarding WaitNextTimeSlice() This function waits until the Thread gets its next slice of time which will occur every 180us.  This causes the loop to execute un-interrupted at a nice periodic rate, actually not real crucial for this case.
> > >  
> > > The curly brackets { } in C are very important.  They group statements into a block.  They must always be in matching pairs.  They can be nested (a block within a block).  The very last end bracket pairs with the begin bracket right after the "for" statement.  This defines the end of the instructions that are in the loop.  You might think of them as an abreviated begin/end statement.   Good programmers indent the lines in their programs so it is easy to see all the statements that are in the same block.  But the blasted email system often messes up the indentation.
> > >  
> > >  
> > > Yes this code fragment must be pasted into a program to be able to test it.  It should be all pasted at the end of the "main" function, but inside the "main" function.  The main function's scope is defined by the the begin/end curly brackets.  The begin bracket is right after the "main" declaration.  The end is further down (skipping over any bracket pairs).  So for example:
> > >  
> > > main()
> > > {   // beginning of main function
> > >     // stuff
> > >  
> > >     // stuff
> > >  
> > >     // stuff
> > >  
> > >     // <<<<<<<Paste your Loop here
> > > }  // end of main function
> > >  
> > > HTH
> > > TK
> > >  
> > >
> > >
> > > ________________________________
> > > From: zeeschuim atmolgers@
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Thursday, November 1, 2012 8:52 AM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >  
> > > Hi Tom
> > >
> > > for(;;) what is this?
> > > {
> > > WaitNextTimeSlice(); what is this?
> > >
> > > if (ReadBit(0)) // if plasma is ON?
> > > {
> > > if (ReadBit(6)) //Up?
> > > {
> > > Delay_sec(1.0); // Delay for error filter
> > > Jog(2,10000); // Axis Z move UP
> > > while (!ReadBit(6)) ;
> > > Jog(2,0);
> > > while (!CheckDone(2)) ;
> > >
> > > }
> > > else if (ReadBit(7)) //DOWN?
> > > {
> > > Delay_sec(1.0); //Delay.
> > > Jog(2,-10000); // Axis Z move DOWN
> > > while (!ReadBit(7)) ;
> > > Jog(2,0);
> > > while (!CheckDone(2)) ;
> > >
> > > }
> > > } twice the same } ?
> > >
> > > Must I paste this code a C progam and run it? or paste it in another progam with my bits in it?
> > >
> > > regards,
> > > Cees
> > >
> > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Cees,
> > > >  
> > > > Do you really need to use that Plasma Screen with the buttons that we don't know what they are supposed to do?
> > > >  
> > > > Regardless, the first step would be develop the Z up/down motion program and get that working.  If you run that program from KMotion while doing a cut does the Z motion up/down happen?  You will of course need to modify it for which Input bits you are wired to.
> > > >  
> > > > The Port and Pins settings in Mach3 are not really necessary.  I don't think they will do anything in Mach3.  This now has to be handled by KFLOP.
> > > >  
> > > > You will also have to remove Z from the Coordinate system as I described.  Eventually we will probably want to be able to switch Z modes dependent on Torch ON, or an M Code, or something. 
> > > >  
> > > > Regards
> > > > TK 
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim <atmolgers@>
> > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > Sent: Wednesday, October 31, 2012 12:13 PM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >  
> > > > Hi Tom
> > > >
> > > > I thought I was ready with your riddles.
> > > > On the Mach plasma screen there are a few buttons related with the thc : torch on off; it is the same function as spindle on/off
> > > > then a button called THC; it is torch enable toggle with OEM code 123 whatever that means
> > > > the next is Reset; with function; Torch Call Zero  with OEM code 124
> > > > what have to be done by the THC inputs is the Z up or down according the both inputs in ports & pins
> > > > what is happening behind all of this I really don't know!
> > > >
> > > > hellup!!
> > > >
> > > > best regards,
> > > > Cees
> > > >
> > > >>
> > >
> >
>
Group: DynoMotion Message: 5963 From: Tom Kerekes Date: 11/5/2012
Subject: Re: torch height control in Mach
Hi Cees,

Your link doesn't work for me so I'm having difficulty understanding what you mean.

I'm guessing the M15 contains a G31 probe?

But yes now do the THC.  Modify the program provided before for your system and have it run (add it to the end of your initialization program loop).  Then in the GCode you can tun a bit on or off to control whether it is in THC or normal Z mode.

Regards
TK

Group: DynoMotion Message: 5967 From: zeeschuim Date: 11/5/2012
Subject: Re: torch height control in Mach
I don't understand how to implement the the THC signals !

bestt regards,
Cees

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> Your link doesn't work for me so I'm having difficulty understanding what you mean.
>
> I'm guessing the M15 contains a G31 probe?
>
> But yes now do the THC.  Modify the program provided before for your system and have it run (add it to the end of your initialization program loop).  Then in the GCode you can tun a bit on or off to control whether it is in THC or normal Z mode.
>
>
> Regards
> TK
>
>
>
> ________________________________
> From: zeeschuim <atmolgers@...>
> To: DynoMotion@yahoogroups.com
> Sent: Monday, November 5, 2012 5:02 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> Yes I use that with  bit 139 and DAC_SERVO_MODE.
> And now I have made a macro M15 what works for me for every time it goes to another cut  contour.
> link to screenshot M15 
>
> In the postprocessor from Vcarve I can implement it before every plunge move. (a new cut contour)
> So that is done, now the THC??
>
> best regards,
> Cees--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Cees,
> >
> > Probing is something independent of THC.  We should go one step at a time.  G31 probing works well under Mach3 but you must configure the NotifyMach3Probe.c program for your particular probe (how it is wired).  Have you tried this?  Let's get probing working first.  See:
> >
> > http://dynomotion.com/Help/Mach3Plugin/Mach3Probe.htm
> >
> >
> > Did you read this?
> >
> >
> > You should only need to change these two defines in the program.  I assume there is some signal available that indicates when the torch touches the metal?
> >
> >
> >       #define PROBE_BIT 0
> >       #define PROBE_ACTIVE_STATE 1
> >
> >
> > No the Plugin can't do this.  It runs under Windows and would be unreliable.
> >
> > Regards
> > TK
> >
> >
> >
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Sunday, November 4, 2012 10:06 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > Hi Tom
> >
> > before it goes in THC mode it has to measure the top of the material.
> > I have tried several macros in Mach3  withtout any luck
> > Is it not possible for you to implement the THC signals in the mach plugin?
> > best regards,
> > Cees
> >
> > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > >
> > >
> > >
> > > Ok Tom
> > >
> > > I will do my best to implement it tomorrow.
> > >
> > > A Plasma file as example:
> > > X an Y jog to the startpoint of the first contour.
> > > Then there is a G31 macro with the torch to measure the height of the startpoint.
> > > Then the torch goes to pierce heigt say 4mm.
> > > Then there is the M3 command to start the plasma.
> > > Z is going to 1,5mm above the surface
> > > then the THC have to start
> > > Start cutting in X and Y, the torch height 1,5mm above the material is monitored and adjust by the THC.
> > > At the end of the contour THC is of, Z is going to jog height and the torch is off.
> > > the next contour is the same as above.
> > >
> > > So the call for the Macro and the start of the torch is in the Gcode, maybee is it possible to implement the THC in the code also??
> > >
> > > thanks,
> > > Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > >
> > > > Hi Cees,
> > > >  
> > > > The "for" statement in C is one way to loop a section of code over and over.  It is a very powerful statement where you can control how the loop operates.  Between the parenthesis you can put 3 things.  The first is a initializor (something to do before the loop starts), the second is the condition to exit the loop, the third is what happens at the end of each loop.  So for example to do the loop 10 times we might initialize a counter, i, to zero, exit when the count is 10, and count 1 at the end of each loop.  So such a "for" statement might look like:
> > > >  
> > > > for (i=0; i<10; i++)
> > > > {
> > > >      // put the stuff to be repeated here
> > > > }
> > > >  
> > > > To loop forever requires no initialization, there is no exit condition, and nothing needs to happen at the end of the loop, so it becomes:
> > > >  
> > > > for (;;)
> > > > {
> > > >     // stuff here gets repeated forever
> > > > }
> > > >  
> > > >  
> > > >  
> > > > Regarding WaitNextTimeSlice() This function waits until the Thread gets its next slice of time which will occur every 180us.  This causes the loop to execute un-interrupted at a nice periodic rate, actually not real crucial for this case.
> > > >  
> > > > The curly brackets { } in C are very important.  They group statements into a block.  They must always be in matching pairs.  They can be nested (a block within a block).  The very last end bracket pairs with the begin bracket right after the "for" statement.  This defines the end of the instructions that are in the loop.  You might think of them as an abreviated begin/end statement.   Good programmers indent the lines in their programs so it is easy to see all the statements that are in the same block.  But the blasted email system often messes up the indentation.
> > > >  
> > > >  
> > > > Yes this code fragment must be pasted into a program to be able to test it.  It should be all pasted at the end of the "main" function, but inside the "main" function.  The main function's scope is defined by the the begin/end curly brackets.  The begin bracket is right after the "main" declaration.  The end is further down (skipping over any bracket pairs).  So for example:
> > > >  
> > > > main()
> > > > {   // beginning of main function
> > > >     // stuff
> > > >  
> > > >     // stuff
> > > >  
> > > >     // stuff
> > > >  
> > > >     // <<<<<<<Paste your Loop here
> > > > }  // end of main function
> > > >  
> > > > HTH
> > > > TK
> > > >  
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Thursday, November 1, 2012 8:52 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >  
> > > > Hi Tom
> > > >
> > > > for(;;) what is this?
> > > > {
> > > > WaitNextTimeSlice(); what is this?
> > > >
> > > > if (ReadBit(0)) // if plasma is ON?
> > > > {
> > > > if (ReadBit(6)) //Up?
> > > > {
> > > > Delay_sec(1.0); // Delay for error filter
> > > > Jog(2,10000); // Axis Z move UP
> > > > while (!ReadBit(6)) ;
> > > > Jog(2,0);
> > > > while (!CheckDone(2)) ;
> > > >
> > > > }
> > > > else if (ReadBit(7)) //DOWN?
> > > > {
> > > > Delay_sec(1.0); //Delay.
> > > > Jog(2,-10000); // Axis Z move DOWN
> > > > while (!ReadBit(7)) ;
> > > > Jog(2,0);
> > > > while (!CheckDone(2)) ;
> > > >
> > > > }
> > > > } twice the same } ?
> > > >
> > > > Must I paste this code a C progam and run it? or paste it in another progam with my bits in it?
> > > >
> > > > regards,
> > > > Cees
> > > >
> > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Cees,
> > > > >  
> > > > > Do you really need to use that Plasma Screen with the buttons that we don't know what they are supposed to do?
> > > > >  
> > > > > Regardless, the first step would be develop the Z up/down motion program and get that working.  If you run that program from KMotion while doing a cut does the Z motion up/down happen?  You will of course need to modify it for which Input bits you are wired to.
> > > > >  
> > > > > The Port and Pins settings in Mach3 are not really necessary.  I don't think they will do anything in Mach3.  This now has to be handled by KFLOP.
> > > > >  
> > > > > You will also have to remove Z from the Coordinate system as I described.  Eventually we will probably want to be able to switch Z modes dependent on Torch ON, or an M Code, or something. 
> > > > >  
> > > > > Regards
> > > > > TK 
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim <atmolgers@>
> > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > Sent: Wednesday, October 31, 2012 12:13 PM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >  
> > > > > Hi Tom
> > > > >
> > > > > I thought I was ready with your riddles.
> > > > > On the Mach plasma screen there are a few buttons related with the thc : torch on off; it is the same function as spindle on/off
> > > > > then a button called THC; it is torch enable toggle with OEM code 123 whatever that means
> > > > > the next is Reset; with function; Torch Call Zero  with OEM code 124
> > > > > what have to be done by the THC inputs is the Z up or down according the both inputs in ports & pins
> > > > > what is happening behind all of this I really don't know!
> > > > >
> > > > > hellup!!
> > > > >
> > > > > best regards,
> > > > > Cees
> > > > >
> > > > >>
> > > >
> > >
> >
>
Group: DynoMotion Message: 5969 From: TK Date: 11/6/2012
Subject: Re: torch height control in Mach
Hi Cees,

I don't understand the question. We have already explained and provided a program that will implement the THC. By "THC signals" does that mean the wiring?  You don't know how to do the wiring?

Regards
TK

On Nov 5, 2012, at 10:58 PM, "zeeschuim" <atmolgers@...> wrote:

 

I don't understand how to implement the the THC signals !

bestt regards,
Cees

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> Your link doesn't work for me so I'm having difficulty understanding what you mean.
>
> I'm guessing the M15 contains a G31 probe?
>
> But yes now do the THC.  Modify the program provided before for your system and have it run (add it to the end of your initialization program loop).  Then in the GCode you can tun a bit on or off to control whether it is in THC or normal Z mode.
>
>
> Regards
> TK
>
>
>
> ________________________________
> From: zeeschuim <atmolgers@...>
> To: DynoMotion@yahoogroups.com
> Sent: Monday, November 5, 2012 5:02 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> Yes I use that with  bit 139 and DAC_SERVO_MODE.
> And now I have made a macro M15 what works for me for every time it goes to another cut  contour.
> link to screenshot M15 
>
> In the postprocessor from Vcarve I can implement it before every plunge move. (a new cut contour)
> So that is done, now the THC??
>
> best regards,
> Cees--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Cees,
> >
> > Probing is something independent of THC.  We should go one step at a time.  G31 probing works well under Mach3 but you must configure the NotifyMach3Probe.c program for your particular probe (how it is wired).  Have you tried this?  Let's get probing working first.  See:
> >
> > http://dynomotion.com/Help/Mach3Plugin/Mach3Probe.htm
> >
> >
> > Did you read this?
> >
> >
> > You should only need to change these two defines in the program.  I assume there is some signal available that indicates when the torch touches the metal?
> >
> >
> >       #define PROBE_BIT 0
> >       #define PROBE_ACTIVE_STATE 1
> >
> >
> > No the Plugin can't do this.  It runs under Windows and would be unreliable.
> >
> > Regards
> > TK
> >
> >
> >
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Sunday, November 4, 2012 10:06 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > Hi Tom
> >
> > before it goes in THC mode it has to measure the top of the material.
> > I have tried several macros in Mach3  withtout any luck
> > Is it not possible for you to implement the THC signals in the mach plugin?
> > best regards,
> > Cees
> >
> > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > >
> > >
> > >
> > > Ok Tom
> > >
> > > I will do my best to implement it tomorrow.
> > >
> > > A Plasma file as example:
> > > X an Y jog to the startpoint of the first contour.
> > > Then there is a G31 macro with the torch to measure the height of the startpoint.
> > > Then the torch goes to pierce heigt say 4mm.
> > > Then there is the M3 command to start the plasma.
> > > Z is going to 1,5mm above the surface
> > > then the THC have to start
> > > Start cutting in X and Y, the torch height 1,5mm above the material is monitored and adjust by the THC.
> > > At the end of the contour THC is of, Z is going to jog height and the torch is off.
> > > the next contour is the same as above.
> > >
> > > So the call for the Macro and the start of the torch is in the Gcode, maybee is it possible to implement the THC in the code also??
> > >
> > > thanks,
> > > Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > >
> > > > Hi Cees,
> > > >  
> > > > The "for" statement in C is one way to loop a section of code over and over.  It is a very powerful statement where you can control how the loop operates.  Between the parenthesis you can put 3 things.  The first is a initializor (something to do before the loop starts), the second is the condition to exit the loop, the third is what happens at the end of each loop.  So for example to do the loop 10 times we might initialize a counter, i, to zero, exit when the count is 10, and count 1 at the end of each loop.  So such a "for" statement might look like:
> > > >  
> > > > for (i=0; i<10; i++)
> > > > {
> > > >      // put the stuff to be repeated here
> > > > }
> > > >  
> > > > To loop forever requires no initialization, there is no exit condition, and nothing needs to happen at the end of the loop, so it becomes:
> > > >  
> > > > for (;;)
> > > > {
> > > >     // stuff here gets repeated forever
> > > > }
> > > >  
> > > >  
> > > >  
> > > > Regarding WaitNextTimeSlice() This function waits until the Thread gets its next slice of time which will occur every 180us.  This causes the loop to execute un-interrupted at a nice periodic rate, actually not real crucial for this case.
> > > >  
> > > > The curly brackets { } in C are very important.  They group statements into a block.  They must always be in matching pairs.  They can be nested (a block within a block).  The very last end bracket pairs with the begin bracket right after the "for" statement.  This defines the end of the instructions that are in the loop.  You might think of them as an abreviated begin/end statement.   Good programmers indent the lines in their programs so it is easy to see all the statements that are in the same block.  But the blasted email system often messes up the indentation.
> > > >  
> > > >  
> > > > Yes this code fragment must be pasted into a program to be able to test it.  It should be all pasted at the end of the "main" function, but inside the "main" function.  The main function's scope is defined by the the begin/end curly brackets.  The begin bracket is right after the "main" declaration.  The end is further down (skipping over any bracket pairs).  So for example:
> > > >  
> > > > main()
> > > > {   // beginning of main function
> > > >     // stuff
> > > >  
> > > >     // stuff
> > > >  
> > > >     // stuff
> > > >  
> > > >     // <<<<<<<Paste your Loop here
> > > > }  // end of main function
> > > >  
> > > > HTH
> > > > TK
> > > >  
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Thursday, November 1, 2012 8:52 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >  
> > > > Hi Tom
> > > >
> > > > for(;;) what is this?
> > > > {
> > > > WaitNextTimeSlice(); what is this?
> > > >
> > > > if (ReadBit(0)) // if plasma is ON?
> > > > {
> > > > if (ReadBit(6)) //Up?
> > > > {
> > > > Delay_sec(1.0); // Delay for error filter
> > > > Jog(2,10000); // Axis Z move UP
> > > > while (!ReadBit(6)) ;
> > > > Jog(2,0);
> > > > while (!CheckDone(2)) ;
> > > >
> > > > }
> > > > else if (ReadBit(7)) //DOWN?
> > > > {
> > > > Delay_sec(1.0); //Delay.
> > > > Jog(2,-10000); // Axis Z move DOWN
> > > > while (!ReadBit(7)) ;
> > > > Jog(2,0);
> > > > while (!CheckDone(2)) ;
> > > >
> > > > }
> > > > } twice the same } ?
> > > >
> > > > Must I paste this code a C progam and run it? or paste it in another progam with my bits in it?
> > > >
> > > > regards,
> > > > Cees
> > > >
> > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Cees,
> > > > >  
> > > > > Do you really need to use that Plasma Screen with the buttons that we don't know what they are supposed to do?
> > > > >  
> > > > > Regardless, the first step would be develop the Z up/down motion program and get that working.  If you run that program from KMotion while doing a cut does the Z motion up/down happen?  You will of course need to modify it for which Input bits you are wired to.
> > > > >  
> > > > > The Port and Pins settings in Mach3 are not really necessary.  I don't think they will do anything in Mach3.  This now has to be handled by KFLOP.
> > > > >  
> > > > > You will also have to remove Z from the Coordinate system as I described.  Eventually we will probably want to be able to switch Z modes dependent on Torch ON, or an M Code, or something. 
> > > > >  
> > > > > Regards
> > > > > TK 
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim <atmolgers@>
> > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > Sent: Wednesday, October 31, 2012 12:13 PM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >  
> > > > > Hi Tom
> > > > >
> > > > > I thought I was ready with your riddles.
> > > > > On the Mach plasma screen there are a few buttons related with the thc : torch on off; it is the same function as spindle on/off
> > > > > then a button called THC; it is torch enable toggle with OEM code 123 whatever that means
> > > > > the next is Reset; with function; Torch Call Zero  with OEM code 124
> > > > > what have to be done by the THC inputs is the Z up or down according the both inputs in ports & pins
> > > > > what is happening behind all of this I really don't know!
> > > > >
> > > > > hellup!!
> > > > >
> > > > > best regards,
> > > > > Cees
> > > > >
> > > > >>
> > > >
> > >
> >
>

Reply via web post Reply to sender
Group: DynoMotion Message: 5971 From: zeeschuim Date: 11/6/2012
Subject: Re: torch height control in Mach
Hi Tom

No the wirering is done , it works.
I see the bits for the THC up, on and down on the digital IO screen getting hi an low.

When I paste the code provided in my init file I get a compile error.
I don't know why.

best regards,
Cees


--- In DynoMotion@yahoogroups.com, TK <tk@...> wrote:
>
> Hi Cees,
>
> I don't understand the question. We have already explained and provided a program that will implement the THC. By "THC signals" does that mean the wiring? You don't know how to do the wiring?
>
> Regards
> TK
>
> On Nov 5, 2012, at 10:58 PM, "zeeschuim" atmolgers@... wrote:
>
> > I don't understand how to implement the the THC signals !
> >
> > bestt regards,
> > Cees
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > >
> > > Hi Cees,
> > >
> > > Your link doesn't work for me so I'm having difficulty understanding what you mean.
> > >
> > > I'm guessing the M15 contains a G31 probe?
> > >
> > > But yes now do the THC. Modify the program provided before for your system and have it run (add it to the end of your initialization program loop). Then in the GCode you can tun a bit on or off to control whether it is in THC or normal Z mode.
> > >
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim atmolgers@
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Monday, November 5, 2012 5:02 AM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > >
> > > Hi Tom
> > >
> > > Yes I use that with bit 139 and DAC_SERVO_MODE.
> > > And now I have made a macro M15 what works for me for every time it goes to another cut contour.
> > > link to screenshot M15
> > >
> > > In the postprocessor from Vcarve I can implement it before every plunge move. (a new cut contour)
> > > So that is done, now the THC??
> > >
> > > best regards,
> > > Cees--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Cees,
> > > >
> > > > Probing is something independent of THC. We should go one step at a time. G31 probing works well under Mach3 but you must configure the NotifyMach3Probe.c program for your particular probe (how it is wired). Have you tried this? Let's get probing working first. See:
> > > >
> > > > http://dynomotion.com/Help/Mach3Plugin/Mach3Probe.htm
> > > >
> > > >
> > > > Did you read this?
> > > >
> > > >
> > > > You should only need to change these two defines in the program. I assume there is some signal available that indicates when the torch touches the metal?
> > > >
> > > >
> > > > Â Â Â Â Â #define PROBE_BIT 0
> > > > Â Â Â Â Â #define PROBE_ACTIVE_STATE 1
> > > >
> > > >
> > > > No the Plugin can't do this. It runs under Windows and would be unreliable.
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Sunday, November 4, 2012 10:06 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >
> > > > Â
> > > > Hi Tom
> > > >
> > > > before it goes in THC mode it has to measure the top of the material.
> > > > I have tried several macros in Mach3 Â withtout any luck
> > > > Is it not possible for you to implement the THC signals in the mach plugin?
> > > > best regards,
> > > > Cees
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > >
> > > > >
> > > > >
> > > > > Ok Tom
> > > > >
> > > > > I will do my best to implement it tomorrow.
> > > > >
> > > > > A Plasma file as example:
> > > > > X an Y jog to the startpoint of the first contour.
> > > > > Then there is a G31 macro with the torch to measure the height of the startpoint.
> > > > > Then the torch goes to pierce heigt say 4mm.
> > > > > Then there is the M3 command to start the plasma.
> > > > > Z is going to 1,5mm above the surface
> > > > > then the THC have to start
> > > > > Start cutting in X and Y, the torch height 1,5mm above the material is monitored and adjust by the THC.
> > > > > At the end of the contour THC is of, Z is going to jog height and the torch is off.
> > > > > the next contour is the same as above.
> > > > >
> > > > > So the call for the Macro and the start of the torch is in the Gcode, maybee is it possible to implement the THC in the code also??
> > > > >
> > > > > thanks,
> > > > > Cees
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > >
> > > > > > Hi Cees,
> > > > > > Â
> > > > > > The "for" statement in C is one way to loop a section of code over and over. It is a very powerful statement where you can control how the loop operates. Between the parenthesis you can put 3 things. The first is a initializor (something to do before the loop starts), the second is the condition to exit the loop, the third is what happens at the end of each loop. So for example to do the loop 10 times we might initialize a counter, i, to zero, exit when the count is 10, and count 1 at the end of each loop. So such a "for" statement might look like:
> > > > > > Â
> > > > > > for (i=0; i<10; i++)
> > > > > > {
> > > > > > Â Â Â Â // put the stuff to be repeated here
> > > > > > }
> > > > > > Â
> > > > > > To loop forever requires no initialization, there is no exit condition, and nothing needs to happen at the end of the loop, so it becomes:
> > > > > > Â
> > > > > > for (;;)
> > > > > > {
> > > > > > Â Â Â Â // stuff here gets repeated forever
> > > > > > }
> > > > > > Â
> > > > > > Â
> > > > > > Â
> > > > > > Regarding WaitNextTimeSlice() This function waits until the Thread gets its next slice of time which will occur every 180us. This causes the loop to execute un-interrupted at a nice periodic rate, actually not real crucial for this case.
> > > > > > Â
> > > > > > The curly brackets { } in C are very important. They group statements into a block. They must always be in matching pairs. They can be nested (a block within a block). The very last end bracket pairs with the begin bracket right after the "for" statement. This defines the end of the instructions that are in the loop. You might think of them as an abreviated begin/end statement.  Good programmers indent the lines in their programs so it is easy to see all the statements that are in the same block. But the blasted email system often messes up the indentation.
> > > > > > Â
> > > > > > Â
> > > > > > Yes this code fragment must be pasted into a program to be able to test it. It should be all pasted at the end of the "main" function, but inside the "main" function. The main function's scope is defined by the the begin/end curly brackets. The begin bracket is right after the "main" declaration. The end is further down (skipping over any bracket pairs). So for example:
> > > > > > Â
> > > > > > main()
> > > > > > {Â Â // beginning of main function
> > > > > > Â Â Â // stuff
> > > > > > Â
> > > > > > Â Â Â // stuff
> > > > > > Â
> > > > > > Â Â Â // stuff
> > > > > > Â
> > > > > > Â Â Â // <<<<<<<Paste your Loop here
> > > > > > }Â // end of main function
> > > > > > Â
> > > > > > HTH
> > > > > > TK
> > > > > > Â
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: zeeschuim atmolgers@
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Thursday, November 1, 2012 8:52 AM
> > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > >
> > > > > > Â
> > > > > > Hi Tom
> > > > > >
> > > > > > for(;;) what is this?
> > > > > > {
> > > > > > WaitNextTimeSlice(); what is this?
> > > > > >
> > > > > > if (ReadBit(0)) // if plasma is ON?
> > > > > > {
> > > > > > if (ReadBit(6)) //Up?
> > > > > > {
> > > > > > Delay_sec(1.0); // Delay for error filter
> > > > > > Jog(2,10000); // Axis Z move UP
> > > > > > while (!ReadBit(6)) ;
> > > > > > Jog(2,0);
> > > > > > while (!CheckDone(2)) ;
> > > > > >
> > > > > > }
> > > > > > else if (ReadBit(7)) //DOWN?
> > > > > > {
> > > > > > Delay_sec(1.0); //Delay.
> > > > > > Jog(2,-10000); // Axis Z move DOWN
> > > > > > while (!ReadBit(7)) ;
> > > > > > Jog(2,0);
> > > > > > while (!CheckDone(2)) ;
> > > > > >
> > > > > > }
> > > > > > } twice the same } ?
> > > > > >
> > > > > > Must I paste this code a C progam and run it? or paste it in another progam with my bits in it?
> > > > > >
> > > > > > regards,
> > > > > > Cees
> > > > > >
> > > > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > >
> > > > > > > Hi Cees,
> > > > > > > ÂÂ
> > > > > > > Do you really need to use that Plasma Screen with the buttons that we don't know what they are supposed to do?
> > > > > > > ÂÂ
> > > > > > > Regardless, the first step would be develop the Z up/down motion program and get that working. If you run that program from KMotion while doing a cut does the Z motion up/down happen? You will of course need to modify it for which Input bits you are wired to.
> > > > > > > ÂÂ
> > > > > > > The Port and Pins settings in Mach3 are not really necessary.  I don't think they will do anything in Mach3. This now has to be handled by KFLOP.
> > > > > > > ÂÂ
> > > > > > > You will also have to remove Z from the Coordinate system as I described. Eventually we will probably want to be able to switch Z modes dependent on Torch ON, or an M Code, or something.ÂÂ
> > > > > > > ÂÂ
> > > > > > > Regards
> > > > > > > TKÂÂ
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: zeeschuim <atmolgers@>
> > > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > > Sent: Wednesday, October 31, 2012 12:13 PM
> > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > >
> > > > > > > ÂÂ
> > > > > > > Hi Tom
> > > > > > >
> > > > > > > I thought I was ready with your riddles.
> > > > > > > On the Mach plasma screen there are a few buttons related with the thc : torch on off; it is the same function as spindle on/off
> > > > > > > then a button called THC; it is torch enable toggle with OEM code 123 whatever that means
> > > > > > > the next is Reset; with function; Torch Call Zero  with OEM code 124
> > > > > > > what have to be done by the THC inputs is the Z up or down according the both inputs in ports & pins
> > > > > > > what is happening behind all of this I really don't know!
> > > > > > >
> > > > > > > hellup!!
> > > > > > >
> > > > > > > best regards,
> > > > > > > Cees
> > > > > > >
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > Reply via web post Reply to sender
>
Group: DynoMotion Message: 5975 From: Tom Kerekes Date: 11/6/2012
Subject: Re: torch height control in Mach
Hi Cees,

The compile error was because you didn't have matching curly brackets {  }.

Each open curly bracket must have a matching close curly bracket just like parenthesis.

Good C programers indent (tab) their code in a way that makes it easy for a human to see which curly brackets pair together to form a block of code.  If you would have indented the code the missing bracket becomes obvious.

There was also a "return" statement in the code before the loop.  This would cause the program to exit before the loop was ever executed.

I have inserted the missing bracket, removed the return, and indented properly and uploaded to a folder for you:

http://tech.groups.yahoo.com/group/DynoMotion/files/Cees%20THC%20Files/

I see you did not change the IO bit numbers in the program.  You have not provided any information on how the THC is wired so I can not check this.

Regards
TK


Group: DynoMotion Message: 5976 From: zeeschuim Date: 11/6/2012
Subject: Re: torch height control in Mach
Thanks Tom!

I will change the bits and the delay time
I really don't know how to progam.
I don't want to know how to progam
I want to cut wood 
I want to cut metal
I want to cut plastic
I know how Mach3 works
is it not enough?

thanks again!
Cees


--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> The compile error was because you didn't have matching curly brackets {  }.
>
> Each open curly bracket must have a matching close curly bracket just like parenthesis.
>
> Good C programers indent (tab) their code in a way that makes it easy for a human to see which curly brackets pair together to form a block of code.  If you would have indented the code the missing bracket becomes obvious.
>
>
> There was also a "return" statement in the code before the loop.  This would cause the program to exit before the loop was ever executed.
>
> I have inserted the missing bracket, removed the return, and indented properly and uploaded to a folder for you:
>
>
> http://tech.groups.yahoo.com/group/DynoMotion/files/Cees%20THC%20Files/
>
>
> I see you did not change the IO bit numbers in the program.  You have not provided any information on how the THC is wired so I can not check this.
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, November 6, 2012 6:03 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> No the wirering is done , it works.
> I see the bits for the THC up, on and down on the digital IO screen getting hi an low.
>
> When I paste the code provided in my init file I get a compile error.
> I don't know why.
>
> best regards,
> Cees
>
>
> --- In DynoMotion@yahoogroups.com, TK tk@ wrote:
> >
> > Hi Cees,
> >
> > I don't understand the question. We have already explained and provided a program that will implement the THC. By "THC signals" does that mean the wiring? You don't know how to do the wiring?
> >
> > Regards
> > TK
> >
> > On Nov 5, 2012, at 10:58 PM, "zeeschuim" atmolgers@ wrote:
> >
> > > I don't understand how to implement the the THC signals !
> > >
> > > bestt regards,
> > > Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > >
> > > > Hi Cees,
> > > >
> > > > Your link doesn't work for me so I'm having difficulty understanding what you mean.
> > > >
> > > > I'm guessing the M15 contains a G31 probe?
> > > >
> > > > But yes now do the THC. Modify the program provided before for your system and have it run (add it to the end of your initialization program loop). Then in the GCode you can tun a bit on or off to control whether it is in THC or normal Z mode.
> > > >
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Monday, November 5, 2012 5:02 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >
> > > >
> > > > Hi Tom
> > > >
> > > > Yes I use that with bit 139 and DAC_SERVO_MODE.
> > > > And now I have made a macro M15 what works for me for every time it goes to another cut contour.
> > > > link to screenshot M15
> > > >
> > > > In the postprocessor from Vcarve I can implement it before every plunge move. (a new cut contour)
> > > > So that is done, now the THC??
> > > >
> > > > best regards,
> > > > Cees--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Cees,
> > > > >
> > > > > Probing is something independent of THC. We should go one step at a time. G31 probing works well under Mach3 but you must configure the NotifyMach3Probe.c program for your particular probe (how it is wired). Have you tried this? Let's get probing working first. See:
> > > > >
> > > > > http://dynomotion.com/Help/Mach3Plugin/Mach3Probe.htm
> > > > >
> > > > >
> > > > > Did you read this?
> > > > >
> > > > >
> > > > > You should only need to change these two defines in the program. I assume there is some signal available that indicates when the torch touches the metal?
> > > > >
> > > > >
> > > > > Â Â Â Â Â #define PROBE_BIT 0
> > > > > Â Â Â Â Â #define PROBE_ACTIVE_STATE 1
> > > > >
> > > > >
> > > > > No the Plugin can't do this. It runs under Windows and would be unreliable.
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim atmolgers@
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Sunday, November 4, 2012 10:06 AM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >
> > > > > Â
> > > > > Hi Tom
> > > > >
> > > > > before it goes in THC mode it has to measure the top of the material.
> > > > > I have tried several macros in Mach3 Â withtout any luck
> > > > > Is it not possible for you to implement the THC signals in the mach plugin?
> > > > > best regards,
> > > > > Cees
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > Ok Tom
> > > > > >
> > > > > > I will do my best to implement it tomorrow.
> > > > > >
> > > > > > A Plasma file as example:
> > > > > > X an Y jog to the startpoint of the first contour.
> > > > > > Then there is a G31 macro with the torch to measure the height of the startpoint.
> > > > > > Then the torch goes to pierce heigt say 4mm.
> > > > > > Then there is the M3 command to start the plasma.
> > > > > > Z is going to 1,5mm above the surface
> > > > > > then the THC have to start
> > > > > > Start cutting in X and Y, the torch height 1,5mm above the material is monitored and adjust by the THC.
> > > > > > At the end of the contour THC is of, Z is going to jog height and the torch is off.
> > > > > > the next contour is the same as above.
> > > > > >
> > > > > > So the call for the Macro and the start of the torch is in the Gcode, maybee is it possible to implement the THC in the code also??
> > > > > >
> > > > > > thanks,
> > > > > > Cees
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > > >
> > > > > > > Hi Cees,
> > > > > > > Â
> > > > > > > The "for" statement in C is one way to loop a section of code over and over. It is a very powerful statement where you can control how the loop operates. Between the parenthesis you can put 3 things. The first is a initializor (something to do before the loop starts), the second is the condition to exit the loop, the third is what happens at the end of each loop. So for example to do the loop 10 times we might initialize a counter, i, to zero, exit when the count is 10, and count 1 at the end of each loop. So such a "for" statement might look like:
> > > > > > > Â
> > > > > > > for (i=0; i<10; i++)
> > > > > > > {
> > > > > > > Â Â Â Â // put the stuff to be repeated here
> > > > > > > }
> > > > > > > Â
> > > > > > > To loop forever requires no initialization, there is no exit condition, and nothing needs to happen at the end of the loop, so it becomes:
> > > > > > > Â
> > > > > > > for (;;)
> > > > > > > {
> > > > > > > Â Â Â Â // stuff here gets repeated forever
> > > > > > > }
> > > > > > > Â
> > > > > > > Â
> > > > > > > Â
> > > > > > > Regarding WaitNextTimeSlice() This function waits until the Thread gets its next slice of time which will occur every 180us. This causes the loop to execute un-interrupted at a nice periodic rate, actually not real crucial for this case.
> > > > > > > Â
> > > > > > > The curly brackets { } in C are very important. They group statements into a block. They must always be in matching pairs. They can be nested (a block within a block). The very last end bracket pairs with the begin bracket right after the "for" statement. This defines the end of the instructions that are in the loop. You might think of them as an abreviated begin/end statement.  Good programmers indent the lines in their programs so it is easy to see all the statements that are in the same block. But the blasted email system often messes up the indentation.
> > > > > > > Â
> > > > > > > Â
> > > > > > > Yes this code fragment must be pasted into a program to be able to test it. It should be all pasted at the end of the "main" function, but inside the "main" function. The main function's scope is defined by the the begin/end curly brackets. The begin bracket is right after the "main" declaration. The end is further down (skipping over any bracket pairs). So for example:
> > > > > > > Â
> > > > > > > main()
> > > > > > > {Â Â // beginning of main function
> > > > > > > Â Â Â // stuff
> > > > > > > Â
> > > > > > > Â Â Â // stuff
> > > > > > > Â
> > > > > > > Â Â Â // stuff
> > > > > > > Â
> > > > > > > Â Â Â // <<<<<<<Paste your Loop here
> > > > > > > }Â // end of main function
> > > > > > > Â
> > > > > > > HTH
> > > > > > > TK
> > > > > > > Â
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: zeeschuim atmolgers@
> > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > Sent: Thursday, November 1, 2012 8:52 AM
> > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > >
> > > > > > > Â
> > > > > > > Hi Tom
> > > > > > >
> > > > > > > for(;;) what is this?
> > > > > > > {
> > > > > > > WaitNextTimeSlice(); what is this?
> > > > > > >
> > > > > > > if (ReadBit(0)) // if plasma is ON?
> > > > > > > {
> > > > > > > if (ReadBit(6)) //Up?
> > > > > > > {
> > > > > > > Delay_sec(1.0); // Delay for error filter
> > > > > > > Jog(2,10000); // Axis Z move UP
> > > > > > > while (!ReadBit(6)) ;
> > > > > > > Jog(2,0);
> > > > > > > while (!CheckDone(2)) ;
> > > > > > >
> > > > > > > }
> > > > > > > else if (ReadBit(7)) //DOWN?
> > > > > > > {
> > > > > > > Delay_sec(1.0); //Delay.
> > > > > > > Jog(2,-10000); // Axis Z move DOWN
> > > > > > > while (!ReadBit(7)) ;
> > > > > > > Jog(2,0);
> > > > > > > while (!CheckDone(2)) ;
> > > > > > >
> > > > > > > }
> > > > > > > } twice the same } ?
> > > > > > >
> > > > > > > Must I paste this code a C progam and run it? or paste it in another progam with my bits in it?
> > > > > > >
> > > > > > > regards,
> > > > > > > Cees
> > > > > > >
> > > > > > > --- In mailto:DynoMotion%40yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > > >
> > > > > > > > Hi Cees,
> > > > > > > > ÃÆ'‚Â
> > > > > > > > Do you really need to use that Plasma Screen with the buttons that we don't know what they are supposed to do?
> > > > > > > > ÃÆ'‚Â
> > > > > > > > Regardless, the first step would beÃÆ'‚Â develop the Z up/down motion program and get that working.ÃÆ'‚Â If you run that program from KMotion while doing a cut does the Z motion up/down happen?ÃÆ'‚Â You will of course need to modify it for which Input bits you are wired to.
> > > > > > > > ÃÆ'‚Â
> > > > > > > > The Port and Pins settings in Mach3 are not really necessary.ÃÆ'‚Â ÃÆ'‚Â I don't think they will do anything in Mach3.ÃÆ'‚Â This now has to beÃÆ'‚Â handled by KFLOP.
> > > > > > > > ÃÆ'‚Â
> > > > > > > > You will also have to remove Z from the Coordinate system as I described.ÃÆ'‚Â Eventually we will probably want to be able to switch Z modes dependent on Torch ON, or an M Code, or something.ÃÆ'‚Â
> > > > > > > > ÃÆ'‚Â
> > > > > > > > Regards
> > > > > > > > TKÃÆ'‚Â
> > > > > > > >
> > > > > > > >
> > > > > > > > ________________________________
> > > > > > > > From: zeeschuim <atmolgers@>
> > > > > > > > To: mailto:DynoMotion%40yahoogroups.com
> > > > > > > > Sent: Wednesday, October 31, 2012 12:13 PM
> > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > >
> > > > > > > > ÃÆ'‚Â
> > > > > > > > Hi Tom
> > > > > > > >
> > > > > > > > I thought I was ready with your riddles.
> > > > > > > > On the Mach plasma screen there are a few buttons related with the thc : torch on off; it is the same function as spindle on/off
> > > > > > > > then a button called THC; it is torch enable toggle with OEM code 123 whatever that means
> > > > > > > > the next is Reset; with function; Torch Call Zero ÃÆ'‚Â with OEM code 124
> > > > > > > > what have to be done by the THC inputs is the Z up or down according the both inputs in ports & pins
> > > > > > > > what is happening behind all of this I really don't know!
> > > > > > > >
> > > > > > > > hellup!!
> > > > > > > >
> > > > > > > > best regards,
> > > > > > > > Cees
> > > > > > > >
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > Reply via web post Reply to sender
> >
>
Group: DynoMotion Message: 5977 From: zeeschuim Date: 11/7/2012
Subject: Re: torch height control in Mach
Hi Tom

I have tried the file you provided whithout any luck.
This  testrun shows it is not working.

Do you have an  idea what is wrong?

regards,
Cees
Group: DynoMotion Message: 5978 From: TK Date: 11/7/2012
Subject: Re: torch height control in Mach
Hi Cees,

Looks like you used the original program with the problems I explained rather than the one I fixed for you. 

Regards
TK

On Nov 7, 2012, at 4:49 AM, "zeeschuim" <atmolgers@...> wrote:

 

Hi Tom


I have tried the file you provided whithout any luck.
This  testrun shows it is not working.

Do you have an  idea what is wrong?

regards,
Cees

Group: DynoMotion Message: 5979 From: zeeschuim Date: 11/7/2012
Subject: Re: torch height control in Mach
kolere, ik krijg er een sik van
--- In DynoMotion@yahoogroups.com, TK <tk@...> wrote:
>
> Hi Cees,
>
> Looks like you used the original program with the problems I explained rather than the one I fixed for you.
>
> Regards
> TK
>
> On Nov 7, 2012, at 4:49 AM, "zeeschuim" <atmolgers@...> wrote:
>
> > Hi Tom
> >
> >
> > I have tried the file you provided whithout any luck.
> > This testrun shows it is not working.
> >
> > Do you have an idea what is wrong?
> >
> > regards,
> > Cees
> >
>
Group: DynoMotion Message: 5980 From: zeeschuim Date: 11/8/2012
Subject: Re: torch height control in Mach
Yes!!   
It is moving!
Only going down, the test progam of my THC give a torch on signal all the time.
And a down signal for 2 seconds, then an up signal for 2 seconds. This loops.

With this test progam the Z axe is going down for two seconds, stops, and going down again for two seconds .
It is never going up, I can't stop this motion, so at the end off its travel it stops on error.

I tried to modify the pause timing in the C progam whithout any difference.
I have modified the velocity and acceleration for Z axe whithout any difference.
In THC mode it is going down until it's end.

Any suggestions?

regards,
Cees
Group: DynoMotion Message: 5981 From: Tom Kerekes Date: 11/8/2012
Subject: Re: torch height control in Mach
Hi Cees,

Well some progress :}

From your video it looks to me like the UP and DOWN test signals are only on for ~1 sec not 2 seconds as you describe.

The Delay Times in the C program are attempting to ignore "short" move commands of 1 second or less.  When the program detects an UP or DOWN signal it first waits 1 second before doing anything.  It the starts Jogging as long as the original signal is still present.  So if the signal goes away within 1 second there will be no motion.

I don't exactly see why that would cause it to move only down.

Anyways please change the Delays to 0.1 sec and re-test.  You mentioned you changed the delays but didn't specify how or what you changed them to.  Please re-post your program afterward so I can check it.

I assume your Z axis can move up and down, correct?

Regards
TK



Group: DynoMotion Message: 5999 From: zeeschuim Date: 11/9/2012
Subject: Re: torch height control in Mach
Hi Tom

About the test progam from the THC module; I can change the output time setting .
This morning I tried with the following settings:
Z axe velocity at 600 mm/min
acceleration at 1000 so it is moving slow but reacting very fast.
The THC test control at 4 seconds.
The delay time in the C progam at 0.1 sec.

in the testrun it was moving down, paused, and moving down, again until it stopped in error.

then I changed the up bit with the down bit.

the second testrun with this new settings it was moving up, paused, moving down, paused,  and moving down again until it stopped in error.
I will send the C progam I used

regards,
Cees
 









--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> Well some progress :}
>
> From your video it looks to me like the UP and DOWN test signals are only on for ~1 sec not 2 seconds as you describe.
>
> The Delay Times in the C program are attempting to ignore "short" move commands of 1 second or less.  When the program detects an UP or DOWN signal it first waits 1 second before doing anything.  It the starts Jogging as long as the original signal is still present.  So if the signal goes away within 1 second there will be no motion.
>
> I don't exactly see why that would cause it to move only down.
>
> Anyways please change the Delays to 0.1 sec and re-test.  You mentioned you changed the delays but didn't specify how or what you changed them to.  Please re-post your program afterward so I can check it.
>
> I assume your Z axis can move up and down, correct?
>
> Regards
> TK
>
>
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Thursday, November 8, 2012 4:34 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Yes!!   
> It is moving!
> Only going down, the test progam of my THC give a torch on signal all the time.
> And a down signal for 2 seconds, then an up signal for 2 seconds. This loops.
>
> With this test progam the Z axe is going down for two seconds, stops, and going down again for two seconds .
> It is never going up, I can't stop this motion, so at the end off its travel it stops on error.
>
> I tried to modify the pause timing in the C progam whithout any difference.
> I have modified the velocity and acceleration for Z axe whithout any difference.
> In THC mode it is going down until it's end.
>
> Any suggestions?
>
> regards,
> Cees
>
Group: DynoMotion Message: 6004 From: Tom Kerekes Date: 11/9/2012
Subject: Re: torch height control in Mach
Hi Cees,

I see now we have the logic backwards.  We want to keep moving:

 WHILE THE BIT IS TRUE 

                while (ReadBit(142)) ;

                while (ReadBit(141)) ;



We currently have to keep moving:

WHILE THE BIT IS NOT TRUE

                while (!ReadBit(142)) ;

                while (!ReadBit(141)) ;


In C the NOT operator is the "!" symbol.

I changed the file and uploaded as Version 3

Please try that.

Regards
TK



Group: DynoMotion Message: 6007 From: zeeschuim Date: 11/9/2012
Subject: Re: torch height control in Mach
Yes,Yes, yes It is working:p

thanks Tom



--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> I see now we have the logic backwards.  We want to keep moving:
>
>  WHILE THE BIT IS TRUE 
>
>                 while (ReadBit(142)) ;
>
>                 while (ReadBit(141)) ;
>
>
>
> We currently have to keep moving:
>
> WHILE THE BIT IS NOT TRUE
>
>                 while (!ReadBit(142)) ;
>
>                 while (!ReadBit(141)) ;
>
>
>
> In C the NOT operator is the "!" symbol.
>
> I changed the file and uploaded as Version 3
>
> Please try that.
>
> Regards
> TK
>
>
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Friday, November 9, 2012 3:03 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> About the test progam from the THC module; I can change the output time setting .
> This morning I tried with the following settings:
> Z axe velocity at 600 mm/min
> acceleration at 1000 so it is moving slow but reacting very fast.
> The THC test control at 4 seconds.
> The delay time in the C progam at 0.1 sec.
>
> in the testrun it was moving down, paused, and moving down, again until it stopped in error.
>
> then I changed the up bit with the down bit.
>
> the second testrun with this new settings it was moving up, paused, moving down, paused,  and moving down again until it stopped in error.
> I will send the C progam I used
>
> regards,
> Cees
>  
>
>
>
>
>
>
>
>
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> >
> > Hi Cees,
> >
> > Well some progress :}
> >
> > From your video it looks to me like the UP and DOWN test signals are only on for ~1 sec not 2 seconds as you describe.
> >
> > The Delay Times in the C program are attempting to ignore "short" move commands of 1 second or less.  When the program detects an UP or DOWN signal it first waits 1 second before doing anything.  It the starts Jogging as long as the original signal is still present.  So if the signal goes away within 1 second there will be no motion.
> >
> > I don't exactly see why that would cause it to move only down.
> >
> > Anyways please change the Delays to 0.1 sec and re-test.  You mentioned you changed the delays but didn't specify how or what you changed them to.  Please re-post your program afterward so I can check it.
> >
> > I assume your Z axis can move up and down, correct?
> >
> > Regards
> > TK
> >
> >
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Thursday, November 8, 2012 4:34 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > Yes!!   
> > It is moving!
> > Only going down, the test progam of my THC give a torch on signal all the time.
> > And a down signal for 2 seconds, then an up signal for 2 seconds. This loops.
> >
> > With this test progam the Z axe is going down for two seconds, stops, and going down again for two seconds .
> > It is never going up, I can't stop this motion, so at the end off its travel it stops on error.
> >
> > I tried to modify the pause timing in the C progam whithout any difference.
> > I have modified the velocity and acceleration for Z axe whithout any difference.
> > In THC mode it is going down until it's end.
> >
> > Any suggestions?
> >
> > regards,
> > Cees
> >
>
Group: DynoMotion Message: 6010 From: Tom Kerekes Date: 11/9/2012
Subject: Re: torch height control in Mach
Yahoo!!  Thanks for your Patience.

But I suspect there are several things more to be added to be able to switch between normal Z and THC mode.

TK


Group: DynoMotion Message: 6015 From: zeeschuim Date: 11/9/2012
Subject: Re: torch height control in Mach
Hi Tom

like what?

best regards

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Yahoo!!  Thanks for your Patience.
>
> But I suspect there are several things more to be added to be able to switch between normal Z and THC mode.
>
> TK
>
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Friday, November 9, 2012 12:53 PM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Yes,Yes, yes It is working
> hij doetet! 
>
> thanks Tom
>
>
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> >
> > Hi Cees,
> >
> > I see now we have the logic backwards.  We want to keep moving:
> >
> >  WHILE THE BIT IS TRUE 
> >
> >                 while (ReadBit(142)) ;
> >
> >                 while (ReadBit(141)) ;
> >
> >
> >
> > We currently have to keep moving:
> >
> > WHILE THE BIT IS NOT TRUE
> >
> >                 while (!ReadBit(142)) ;
> >
> >                 while (!ReadBit(141)) ;
> >
> >
> >
> > In C the NOT operator is the "!" symbol.
> >
> > I changed the file and uploaded as Version 3
> >
> > Please try that.
> >
> > Regards
> > TK
> >
> >
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Friday, November 9, 2012 3:03 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > Hi Tom
> >
> > About the test progam from the THC module; I can change the output time setting .
> > This morning I tried with the following settings:
> > Z axe velocity at 600 mm/min
> > acceleration at 1000 so it is moving slow but reacting very fast.
> > The THC test control at 4 seconds.
> > The delay time in the C progam at 0.1 sec.
> >
> > in the testrun it was moving down, paused, and moving down, again until it stopped in error.
> >
> > then I changed the up bit with the down bit.
> >
> > the second testrun with this new settings it was moving up, paused, moving down, paused,  and moving down again until it stopped in error.
> > I will send the C progam I used
> >
> > regards,
> > Cees
> >  
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > >
> > > Hi Cees,
> > >
> > > Well some progress :}
> > >
> > > From your video it looks to me like the UP and DOWN test signals are only on for ~1 sec not 2 seconds as you describe.
> > >
> > > The Delay Times in the C program are attempting to ignore "short" move commands of 1 second or less.  When the program detects an UP or DOWN signal it first waits 1 second before doing anything.  It the starts Jogging as long as the original signal is still present.  So if the signal goes away within 1 second there will be no motion.
> > >
> > > I don't exactly see why that would cause it to move only down.
> > >
> > > Anyways please change the Delays to 0.1 sec and re-test.  You mentioned you changed the delays but didn't specify how or what you changed them to.  Please re-post your program afterward so I can check it.
> > >
> > > I assume your Z axis can move up and down, correct?
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim atmolgers@
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Thursday, November 8, 2012 4:34 AM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > >  
> > > Yes!!   
> > > It is moving!
> > > Only going down, the test progam of my THC give a torch on signal all the time.
> > > And a down signal for 2 seconds, then an up signal for 2 seconds. This loops.
> > >
> > > With this test progam the Z axe is going down for two seconds, stops, and going down again for two seconds .
> > > It is never going up, I can't stop this motion, so at the end off its travel it stops on error.
> > >
> > > I tried to modify the pause timing in the C progam whithout any difference.
> > > I have modified the velocity and acceleration for Z axe whithout any difference.
> > > In THC mode it is going down until it's end.
> > >
> > > Any suggestions?
> > >
> > > regards,
> > > Cees
> > >
> >
>
Group: DynoMotion Message: 6017 From: zeeschuim Date: 11/10/2012
Subject: Re: torch height control in Mach
Hi Tom

It is not working in a G-code program.
The Z axe shakes a bit after the M15 G31 macro
I have tried to change the pause time from 0,1 to 1 second with no luck.
With an delay of one second there is no THC movement at all, only the normal progam.
I have changed the Windows ahead time to 1 sec with no luck
In the postprocessor I changed something after the macro so there are no Z movements anymore until the torch goes of.
No luck!

any sugestions?

regards,
Cees

--- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@...> wrote:
>
> Hi Tom
> like what?
> best regards
> --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> >
> > Yahoo!! Thanks for your Patience.
> >
> > But I suspect there are several things more to be added to be able to
> switch between normal Z and THC mode.
> >
> > TK
> >
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Friday, November 9, 2012 12:53 PM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> > Â
> > Yes,Yes, yes It is working
> > hij doetet!Â
> >
> > thanks Tom
> >
> >
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > >
> > > Hi Cees,
> > >
> > > I see now we have the logic backwards. We want to keep
> moving:
> > >
> > >  WHILE THE BIT IS TRUEÂÂ
> > >
> > >        ÂÂ
>     while (ReadBit(142)) ;
> > >
> > >        ÂÂ
>     while (ReadBit(141)) ;
> > >
> > >
> > >
> > > We currently have to keep moving:
> > >
> > > WHILE THE BIT IS NOT TRUE
> > >
> > >        ÂÂ
>     while (!ReadBit(142)) ;
> > >
> > >        ÂÂ
>     while (!ReadBit(141)) ;
> > >
> > >
> > >
> > > In C the NOT operator is the "!" symbol.
> > >
> > > I changed the file and uploaded as Version 3
> > >
> > > Please try that.
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim atmolgers@
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Friday, November 9, 2012 3:03 AM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > > ÂÂ
> > > Hi Tom
> > >
> > > About the test progam from the THC module; I can change the output
> time setting .
> > > This morning I tried with the following settings:
> > > Z axe velocity at 600 mm/min
> > > acceleration at 1000 so it is moving slow but reacting very fast.
> > > The THC test control at 4 seconds.
> > > The delay time in the C progam at 0.1 sec.
> > >
> > > in the testrun it was moving down, paused, and moving down, again
> until it stopped in error.
> > >
> > > then I changed the up bit with the down bit.
> > >
> > > the second testrun with this new settings it was moving up, paused,
> moving down, paused,  and moving down again until it stopped in
> error.
> > > I will send the C progam I used
> > >
> > > regards,
> > > Cees
> > > ÂÂ
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > >
> > > > Hi Cees,
> > > >
> > > > Well some progress :}
> > > >
> > > > From your video it looks to me like the UP and DOWN test signals
> are only on for ~1 sec not 2 seconds as you describe.
> > > >
> > > > The Delay Times in the C program are attempting to ignore "short"
> move commands of 1 second or less. When the program
> detects an UP or DOWN signal it first waits 1 second before doing
> anything. It the starts Jogging as long as the original
> signal is still present. So if the signal goes away
> within 1 second there will be no motion.
> > > >
> > > > I don't exactly see why that would cause it to move only down.
> > > >
> > > > Anyways please change the Delays to 0.1 sec and
> re-test. You mentioned you changed the delays but didn't
> specify how or what you changed them to. Please re-post
> your program afterward so I can check it.
> > > >
> > > > I assume your Z axis can move up and down, correct?
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Thursday, November 8, 2012 4:34 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >
> > > > ÂÂÂ
> > > > Yes!!  ÂÂÂ
> > > > It is moving!
> > > > Only going down, the test progam of my THC give a torch on signal
> all the time.
> > > > And a down signal for 2 seconds, then an up signal for 2 seconds.
> This loops.
> > > >
> > > > With this test progam the Z axe is going down for two seconds,
> stops, and going down again for two seconds .
> > > > It is never going up, I can't stop this motion, so at the end off
> its travel it stops on error.
> > > >
> > > > I tried to modify the pause timing in the C progam whithout any
> difference.
> > > > I have modified the velocity and acceleration for Z axe whithout
> any difference.
> > > > In THC mode it is going down until it's end.
> > > >
> > > > Any suggestions?
> > > >
> > > > regards,
> > > > Cees
> > > >
> > >
> >
>
Group: DynoMotion Message: 6020 From: zeeschuim Date: 11/10/2012
Subject: Re: torch height control in Mach
Hi Tom

On the torchmate plasmacutter  site driver  they explain how the driver for the plasma cutter works.
They speak about X and Y movements and never about the Z movement, I think the Z movement is totally  out of the cooordinate system.
I think it is moved by the G31 macro and then by the THC.

what do you think?

Cees

 
--- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@...> wrote:
>
> Hi Tom
> It is not working in a G-code program.The Z axe shakes a bit after the
> M15 G31 macroI have tried to change the pause time from 0,1 to 1 second
> with no luck.With an delay of one second there is no THC movement at
> all, only the normal progam.I have changed the Windows ahead time to 1
> sec with no luckIn the postprocessor I changed something after the macro
> so there are no Z movements anymore until the torch goes of.No luck!
> any sugestions?
> regards,Cees
> --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> >
> > Hi Tom
> > like what?
> > best regards
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > >
> > > Yahoo!! Thanks for your Patience.
> > >
> > > But I suspect there are several things more to be added to be able
> to
> > switch between normal Z and THC mode.
> > >
> > > TK
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim atmolgers@
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Friday, November 9, 2012 12:53 PM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > > Â
> > > Yes,Yes, yes It is working
> > > hij doetet!Â
> > >
> > > thanks Tom
> > >
> > >
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > >
> > > > Hi Cees,
> > > >
> > > > I see now we have the logic backwards. We want to keep
> > moving:
> > > >
> > > >  WHILE THE BIT IS TRUEÂÂ
> > > >
> > > >        ÂÂ
> >     while (ReadBit(142)) ;
> > > >
> > > >        ÂÂ
> >     while (ReadBit(141)) ;
> > > >
> > > >
> > > >
> > > > We currently have to keep moving:
> > > >
> > > > WHILE THE BIT IS NOT TRUE
> > > >
> > > >        ÂÂ
> >     while (!ReadBit(142)) ;
> > > >
> > > >        ÂÂ
> >     while (!ReadBit(141)) ;
> > > >
> > > >
> > > >
> > > > In C the NOT operator is the "!" symbol.
> > > >
> > > > I changed the file and uploaded as Version 3
> > > >
> > > > Please try that.
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Friday, November 9, 2012 3:03 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >
> > > > ÂÂ
> > > > Hi Tom
> > > >
> > > > About the test progam from the THC module; I can change the output
> > time setting .
> > > > This morning I tried with the following settings:
> > > > Z axe velocity at 600 mm/min
> > > > acceleration at 1000 so it is moving slow but reacting very fast.
> > > > The THC test control at 4 seconds.
> > > > The delay time in the C progam at 0.1 sec.
> > > >
> > > > in the testrun it was moving down, paused, and moving down, again
> > until it stopped in error.
> > > >
> > > > then I changed the up bit with the down bit.
> > > >
> > > > the second testrun with this new settings it was moving up,
> paused,
> > moving down, paused,  and moving down again until it stopped in
> > error.
> > > > I will send the C progam I used
> > > >
> > > > regards,
> > > > Cees
> > > > ÂÂ
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > >
> > > > > Hi Cees,
> > > > >
> > > > > Well some progress :}
> > > > >
> > > > > From your video it looks to me like the UP and DOWN test signals
> > are only on for ~1 sec not 2 seconds as you describe.
> > > > >
> > > > > The Delay Times in the C program are attempting to ignore
> "short"
> > move commands of 1 second or less. When the program
> > detects an UP or DOWN signal it first waits 1 second before doing
> > anything. It the starts Jogging as long as the
> original
> > signal is still present. So if the signal goes away
> > within 1 second there will be no motion.
> > > > >
> > > > > I don't exactly see why that would cause it to move only down.
> > > > >
> > > > > Anyways please change the Delays to 0.1 sec and
> > re-test. You mentioned you changed the delays but
> didn't
> > specify how or what you changed them to. Please
> re-post
> > your program afterward so I can check it.
> > > > >
> > > > > I assume your Z axis can move up and down, correct?
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim atmolgers@
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Thursday, November 8, 2012 4:34 AM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >
> > > > > ÂÂÂ
> > > > > Yes!!  ÂÂÂ
> > > > > It is moving!
> > > > > Only going down, the test progam of my THC give a torch on
> signal
> > all the time.
> > > > > And a down signal for 2 seconds, then an up signal for 2
> seconds.
> > This loops.
> > > > >
> > > > > With this test progam the Z axe is going down for two seconds,
> > stops, and going down again for two seconds .
> > > > > It is never going up, I can't stop this motion, so at the end
> off
> > its travel it stops on error.
> > > > >
> > > > > I tried to modify the pause timing in the C progam whithout any
> > difference.
> > > > > I have modified the velocity and acceleration for Z axe whithout
> > any difference.
> > > > > In THC mode it is going down until it's end.
> > > > >
> > > > > Any suggestions?
> > > > >
> > > > > regards,
> > > > > Cees
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6021 From: Tom Kerekes Date: 11/10/2012
Subject: Re: torch height control in Mach
Hi Cees,

I think you are correct.  The way we are now has the Z axis being driven both by the GCode Coordinated Motion System and the THC Jogs.  This is basically like telling the motor to go to two different places at the same time.

I think we require two modes of operation.  The Z axis can be added and removed from GCode control with the statements shown below:


            // Plasma is on switch, remove Z from System to allow THC
            DefineCoordSystem(0,1,-1,-1);



            // Plasma is off switch to normal Z mode
            DefineCoordSystem(0,1,2,-1);


It just isn't clear to me what signal we should use to switch modes.  Let's try using the Torch ON signal coming from the unit.  Although it isn't totally clear to me what that is.  Does that indicate that the arc is turned on?  Or that the arc is ready?  Maybe it would be better to have a separate bit that we can switch independently of all that?  Anyway let's try using the Torch ON signal.  I've modified the C program as V4 and uploaded it.  Please give it a try.

Regards
TK


Group: DynoMotion Message: 6022 From: zeeschuim Date: 11/10/2012
Subject: Re: torch height control in Mach
Hi Tom

I will try it tomorrow
At the G31 macro the Z axe goes to pierceheight, 5mm, then switch the torch  on.
After the torch is on the Z axe will go to 1.5mm cutheight.
At cutheight 1.5mm we can Mach3 do an output.
All this can happen in the same G31 macro.
We use this output for a kanalog input and use it as the     // Plasma is on switch, remove Z from System to allow THC
             DefineCoordSystem(0,1,-1,-1);

make this sense?
regards,
Cees

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> I think you are correct.  The way we are now has the Z axis being driven both by the GCode Coordinated Motion System and the THC Jogs.  This is basically like telling the motor to go to two different
> places at the same time.
>
> I think we require two modes of operation.  The Z axis can be added and removed from GCode control with the statements shown below:
>
>
>             // Plasma is on switch, remove Z from System to allow THC
>             DefineCoordSystem(0,1,-1,-1);
>
>
>
>
>             // Plasma is off switch to normal Z mode
>             DefineCoordSystem(0,1,2,-1);
>
>
>
> It just isn't clear to me what signal we should use to switch modes.  Let's try using the Torch ON signal coming from the unit.  Although it isn't totally clear to me what that is.  Does that indicate that the arc is turned on?  Or that the arc is ready?  Maybe it would be better to have a separate bit that we can switch independently of all that?  Anyway let's try using the Torch ON signal.  I've modified the C program as V4 and uploaded it.  Please give it a try.
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Saturday, November 10, 2012 7:50 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> On the torchmate plasmacutter  sitedriver  they explain how the driver for the plasma cutter works.
> They speak about X and Y movements and never about the Z movement, I think the Z movement is totally  out of the cooordinate system.
> I think it is moved by the G31 macro and then by the THC.
>
> what do you think?
>
> Cees
>
Group: DynoMotion Message: 6023 From: Tom Kerekes Date: 11/10/2012
Subject: Re: torch height control in Mach
Hi Cees,

If I understand you correctly.  Using Torch On to switch modes will not work, because after the Torch is switched on we still need to move Z to the 1.5mm height from GCode.  So we need a different command (or bit) other than Torch On to switch modes.

OK let's use an output "bit" that Mach3 can turn on and off to change modes.  We don't need a real physical bit that we output and wire back into a Kanalog Input Bit.  We can simply use a KFLOP Virtual Bit.  These are designed exactly for this type of purpose.  It is like a flag that exists only inside KFLOP that Mach3 can turn on and off like a real output bit, but KFLOP can also observe and test like an input.  Let's use Virtual Bit #48. 

Do you know how to configure an output bit in the Mach3 Config | Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from the Mach3 Macro?

I've uploaded a V5 that uses bit48 to change modes.

Let me know how much of this makes sense.

Regards
TK



Group: DynoMotion Message: 6024 From: bennyattwell Date: 11/10/2012
Subject: Re: torch height control in Mach
you will find you need to wait about half a second depending on material for the arc voltage to stabilise at cut height before switching on thc, or torch may dive into the material.

ideally you will need seperate on/off macros which can be called from g code.
for example if cutting small holes you wont use thc.
you may also want to switch it off on some corners or below certain speeds (for speeds it would be better to have it monitored automatically)

--- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@...> wrote:
>
> Hi Tom
> I will try it tomorrowAt the G31 macro the Z axe goes to pierceheight,
> 5mm, then switch the torch on.After the torch is on the Z axe will go
> to 1.5mm cutheight.At cutheight 1.5mm we can Mach3 do an output.All this
> can happen in the same G31 macro.We use this output for a kanalog input
> and use it as the // Plasma is on switch, remove Z from System to
> allow THC
> DefineCoordSystem(0,1,-1,-1);
> make this sense?regards,Cees
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Cees,
> >
> > I think you are correct. The way we are now has the Z axis being
> driven both by the GCode Coordinated Motion System and the THC Jogs.
> This is basically like telling the motor to go to two different
> > places at the same time.
> >
> > I think we require two modes of operation. The Z axis can be added
> and removed from GCode control with the statements shown below:
> >
> >
> > // Plasma is on switch, remove Z from System to allow THC
> > DefineCoordSystem(0,1,-1,-1);
> >
> >
> >
> >
> > // Plasma is off switch to normal Z mode
> > DefineCoordSystem(0,1,2,-1);
> >
> >
> >
> > It just isn't clear to me what signal we should use to switch modes.
> Let's try using the Torch ON signal coming from the unit. Although it
> isn't totally clear to me what that is. Does that indicate that the arc
> is turned on? Or that the arc is ready? Maybe it would be better to
> have a separate bit that we can switch independently of all that?
> Anyway let's try using the Torch ON signal. I've modified the C program
> as V4 and uploaded it. Please give it a try.
> >
> > Regards
> > TK
> >
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Saturday, November 10, 2012 7:50 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >
> > Hi Tom
> >
> > On the torchmate plasmacutter sitedriver they explain how the driver
> for the plasma cutter works.
> > They speak about X and Y movements and never about the Z movement, I
> think the Z movement is totally out of the cooordinate system.
> > I think it is moved by the G31 macro and then by the THC.
> >
> > what do you think?
> >
> > Cees
> >
>
Group: DynoMotion Message: 6026 From: bennyattwell Date: 11/10/2012
Subject: Re: torch height control in Mach
sorry for butting in on this but im following the thread with interest as im thinking of running my plasma on kflop.
and now you have modbus working i may also use one on one of my big machining centre conversions ( which i couldnt do before due to not enough i/o from kflop)
Group: DynoMotion Message: 6027 From: zeeschuim Date: 11/10/2012
Subject: Re: torch height control in Mach
Hi Tom

Yes I think I can do that.
It is pin 48 on port 1? am I right?
To close this pin 48 output,  the torch on/of bit can be used?

In the postprocessor it will be:
+  Commands output for Plunge Moves
+---------------------------------------------------
begin PLUNGE_MOVE

"M15" // this the G31 macro to measure the top of the material, go to pierceheight,  torch on, go to cutheight, do output 3 ( pin48 port 1)

then cutting with THcontrol

torch of bit  wil close pin48 and  // Plasma is off switch to normal Z mode
 DefineCoordSystem(0,1,2,-1); 

this should be ok, don't you think?

regards,
Cees


--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> If I understand you correctly.  Using Torch On to switch modes will not work, because after the Torch is switched on we still need to move Z to the 1.5mm height from GCode.  So we need a different command (or bit) other than Torch On to switch modes.
>
> OK let's use an output "bit" that Mach3 can turn on and off to change modes.  We don't need a real physical bit that we output and wire back into a Kanalog Input Bit.  We can simply use a KFLOP Virtual Bit.  These are designed exactly for this type of purpose.  It is like a flag that exists only inside KFLOP that Mach3 can turn on and off like a real output bit, but KFLOP can also observe and test like an input.  Let's use Virtual Bit #48. 
>
>
> Do you know how to configure an output bit in the Mach3 Config | Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from the Mach3 Macro?
>
> I've uploaded a V5 that uses bit48 to change modes.
>
> Let me know how much of this makes sense.
>
> Regards
> TK
>
>
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Saturday, November 10, 2012 10:35 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> I will try it tomorrow
> At the G31 macro the Z axe goes to pierceheight, 5mm, then switch the torch  on.
> After the torch is on the Z axe will go to 1.5mm cutheight.
> At cutheight 1.5mm we can Mach3 do an output.
> All this can happen in the same G31 macro.
> We use this output for a kanalog input and use it as the    // Plasma is on switch, remove Z from System to allow THC
>              DefineCoordSystem(0,1,-1,-1);
>
> make this sense?
> regards,
> Cees
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> >
> > Hi Cees,
> >
> > I think you are correct.  The way we are now has the Z axis being driven both by the GCode Coordinated Motion System and the THC Jogs.  This is basically like telling the motor to go to two different
> > places at the same time.
> >
> > I think we require two modes of operation.  The Z axis can be added and removed from GCode control with the statements shown below:
> >
> >
> >             // Plasma is on switch, remove Z from System to allow THC
> >             DefineCoordSystem(0,1,-1,-1);
> >
> >
> >
> >
> >             // Plasma is off switch to normal Z mode
> >             DefineCoordSystem(0,1,2,-1);
> >
> >
> >
> > It just isn't clear to me what signal we should use to switch modes.  Let's try using the Torch ON signal coming from the unit.  Although it isn't totally clear to me what that is.  Does that indicate that the arc is turned on?  Or that the arc is ready?  Maybe it would be better to have a separate bit that we can switch independently of all that?  Anyway let's try using the Torch ON signal.  I've modified the C program as V4 and uploaded it.  Please give it a try.
> >
> > Regards
> > TK
> >
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Saturday, November 10, 2012 7:50 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > Hi Tom
> >
> > On the torchmate plasmacutter  sitedriver  they explain how the driver for the plasma cutter works.
> > They speak about X and Y movements and never about the Z movement, I think the Z movement is totally  out of the cooordinate system.
> > I think it is moved by the G31 macro and then by the THC.
> >
> > what do you think?
> >
> > Cees
> >
>
Group: DynoMotion Message: 6030 From: zeeschuim Date: 11/11/2012
Subject: Re: torch height control in Mach
I don't know it anymore


--- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@...> wrote:
>
> Hi Tom
> Yes I think I can do that.It is pin 48 on port 1? am I right?To close
> this pin 48 output, the torch on/of bit can be used?
> In the postprocessor it will be:+ Commands output for Plunge
> Moves+---------------------------------------------------begin
> PLUNGE_MOVE
> "M15" // this the G31 macro to measure the top of the material, go to
> pierceheight, torch on, go to cutheight, do output 3 ( pin48 port 1)
> then cutting with THcontrol
> torch of bit wil close pin48 and // Plasma is off switch to normal Z
> mode
> DefineCoordSystem(0,1,2,-1);
> this should be ok, don't you think?
> regards,Cees
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Cees,
> >
> > If I understand you correctly. Using Torch On to switch modes
> will not work, because after the Torch is switched on we still need to
> move Z to the 1.5mm height from GCode. So we need a different
> command (or bit) other than Torch On to switch modes.
> >
> > OK let's use an output "bit" that Mach3 can turn on and off to change
> modes. We don't need a real physical bit that we output and wire
> back into a Kanalog Input Bit. We can simply use a KFLOP Virtual
> Bit. These are designed exactly for this type of purpose. It
> is like a flag that exists only inside KFLOP that Mach3 can turn on and
> off like a real output bit, but KFLOP can also observe and test like an
> input. Let's use Virtual Bit #48.Â
> >
> >
> > Do you know how to configure an output bit in the Mach3 Config |
> Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from the
> Mach3 Macro?
> >
> > I've uploaded a V5 that uses bit48 to change modes.
> >
> > Let me know how much of this makes sense.
> >
> > Regards
> > TK
> >
> >
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Saturday, November 10, 2012 10:35 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> > Â
> > Hi Tom
> >
> > I will try it tomorrow
> > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch the
> torch  on.
> > After the torch is on the Z axe will go to 1.5mm cutheight.
> > At cutheight 1.5mm we can Mach3 do an output.
> > All this can happen in the same G31 macro.
> > We use this output for a kanalog input and use it as the  Â
> // Plasma is on switch, remove Z from System to allow THC
> > Â Â Â Â Â Â Â DefineCoordSystem(0,1,-1,-1);
> >
> > make this sense?
> > regards,
> > Cees
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > >
> > > Hi Cees,
> > >
> > > I think you are correct. The way we are now has the Z axis
> being driven both by the GCode Coordinated Motion System and the THC
> Jogs. This is basically like telling the motor to go to two
> different
> > > places at the same time.
> > >
> > > I think we require two modes of operation. The Z axis can be
> added and removed from GCode control with the statements shown below:
> > >
> > >
> > > Â Â Â Â Â Â Â Â Â // Plasma is on
> switch, remove Z from System to allow THC
> > > Â Â Â Â Â Â Â Â Â
> DefineCoordSystem(0,1,-1,-1);
> > >
> > >
> > >
> > >
> > > Â Â Â Â Â Â Â Â Â // Plasma is off
> switch to normal Z mode
> > > Â Â Â Â Â Â Â Â Â
> DefineCoordSystem(0,1,2,-1);
> > >
> > >
> > >
> > > It just isn't clear to me what signal we should use to switch
> modes. Let's try using the Torch ON signal coming from the
> unit. Although it isn't totally clear to me what that is. Does
> that indicate that the arc is turned on? Or that the arc is
> ready? Maybe it would be better to have a separate bit that we can
> switch independently of all that? Anyway let's try using the Torch
> ON signal. I've modified the C program as V4 and uploaded it.Â
> Please give it a try.
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim atmolgers@
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Saturday, November 10, 2012 7:50 AM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > > Â
> > > Hi Tom
> > >
> > > On the torchmate plasmacutter  sitedriver  they explain
> how the driver for the plasma cutter works.
> > > They speak about X and Y movements and never about the Z movement, I
> think the Z movement is totally  out of the cooordinate system.
> > > I think it is moved by the G31 macro and then by the THC.
> > >
> > > what do you think?
> > >
> > > Cees
> > >
> >
>
Group: DynoMotion Message: 6034 From: zeeschuim Date: 11/12/2012
Subject: Re: torch height control in Mach
Never try to close an output 10
With a macro M14 what is telling to do" DeActivateSignal(Output4)"
It is NOT!! going to work!#-o

regards,
Cees


--- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@...> wrote:
>
> I don't know it anymore
>
>
> --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> >
> > Hi Tom
> > Yes I think I can do that.It is pin 48 on port 1? am I right?To close
> > this pin 48 output, the torch on/of bit can be used?
> > In the postprocessor it will be:+ Commands output for Plunge
> > Moves+---------------------------------------------------begin
> > PLUNGE_MOVE
> > "M15" // this the G31 macro to measure the top of the material, go to
> > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port 1)
> > then cutting with THcontrol
> > torch of bit wil close pin48 and // Plasma is off switch to normal Z
> > mode
> > DefineCoordSystem(0,1,2,-1);
> > this should be ok, don't you think?
> > regards,Cees
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Cees,
> > >
> > > If I understand you correctly. Using Torch On to switch modes
> > will not work, because after the Torch is switched on we still need to
> > move Z to the 1.5mm height from GCode. So we need a different
> > command (or bit) other than Torch On to switch modes.
> > >
> > > OK let's use an output "bit" that Mach3 can turn on and off to change
> > modes. We don't need a real physical bit that we output and wire
> > back into a Kanalog Input Bit. We can simply use a KFLOP Virtual
> > Bit. These are designed exactly for this type of purpose. It
> > is like a flag that exists only inside KFLOP that Mach3 can turn on and
> > off like a real output bit, but KFLOP can also observe and test like an
> > input. Let's use Virtual Bit #48.Â
> > >
> > >
> > > Do you know how to configure an output bit in the Mach3 Config |
> > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from the
> > Mach3 Macro?
> > >
> > > I've uploaded a V5 that uses bit48 to change modes.
> > >
> > > Let me know how much of this makes sense.
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim atmolgers@
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Saturday, November 10, 2012 10:35 AM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > > Â
> > > Hi Tom
> > >
> > > I will try it tomorrow
> > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch the
> > torch  on.
> > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > At cutheight 1.5mm we can Mach3 do an output.
> > > All this can happen in the same G31 macro.
> > > We use this output for a kanalog input and use it as the  Â
> > // Plasma is on switch, remove Z from System to allow THC
> > > Â Â Â Â Â Â Â DefineCoordSystem(0,1,-1,-1);
> > >
> > > make this sense?
> > > regards,
> > > Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > >
> > > > Hi Cees,
> > > >
> > > > I think you are correct. The way we are now has the Z axis
> > being driven both by the GCode Coordinated Motion System and the THC
> > Jogs. This is basically like telling the motor to go to two
> > different
> > > > places at the same time.
> > > >
> > > > I think we require two modes of operation. The Z axis can be
> > added and removed from GCode control with the statements shown below:
> > > >
> > > >
> > > > Â Â Â Â Â Â Â Â Â // Plasma is on
> > switch, remove Z from System to allow THC
> > > > Â Â Â Â Â Â Â Â Â
> > DefineCoordSystem(0,1,-1,-1);
> > > >
> > > >
> > > >
> > > >
> > > > Â Â Â Â Â Â Â Â Â // Plasma is off
> > switch to normal Z mode
> > > > Â Â Â Â Â Â Â Â Â
> > DefineCoordSystem(0,1,2,-1);
> > > >
> > > >
> > > >
> > > > It just isn't clear to me what signal we should use to switch
> > modes. Let's try using the Torch ON signal coming from the
> > unit. Although it isn't totally clear to me what that is. Does
> > that indicate that the arc is turned on? Or that the arc is
> > ready? Maybe it would be better to have a separate bit that we can
> > switch independently of all that? Anyway let's try using the Torch
> > ON signal. I've modified the C program as V4 and uploaded it.Â
> > Please give it a try.
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >
> > > > Â
> > > > Hi Tom
> > > >
> > > > On the torchmate plasmacutter  sitedriver  they explain
> > how the driver for the plasma cutter works.
> > > > They speak about X and Y movements and never about the Z movement, I
> > think the Z movement is totally  out of the cooordinate system.
> > > > I think it is moved by the G31 macro and then by the THC.
> > > >
> > > > what do you think?
> > > >
> > > > Cees
> > > >
> > >
> >
>
Group: DynoMotion Message: 6037 From: zeeschuim Date: 11/12/2012
Subject: Re: torch height control in Mach
Hi Tom

All the progams are working!
Only I have to tame the Polish THC
It is going like a drunken sailor!

Thanks for the help!
Cees


--- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@...> wrote:
>
> Never try to close an output 10With a macro M14 what is telling to do"
> DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> regards,Cees
>
> --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> >
> > I don't know it anymore
> >
> >
> > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > >
> > > Hi Tom
> > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> close
> > > this pin 48 output, the torch on/of bit can be used?
> > > In the postprocessor it will be:+ Commands output for Plunge
> > > Moves+---------------------------------------------------begin
> > > PLUNGE_MOVE
> > > "M15" // this the G31 macro to measure the top of the material, go
> to
> > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> 1)
> > > then cutting with THcontrol
> > > torch of bit wil close pin48 and // Plasma is off switch to normal
> Z
> > > mode
> > > DefineCoordSystem(0,1,2,-1);
> > > this should be ok, don't you think?
> > > regards,Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Cees,
> > > >
> > > > If I understand you correctly. Using Torch On to switch modes
> > > will not work, because after the Torch is switched on we still need
> to
> > > move Z to the 1.5mm height from GCode. So we need a different
> > > command (or bit) other than Torch On to switch modes.
> > > >
> > > > OK let's use an output "bit" that Mach3 can turn on and off to
> change
> > > modes. We don't need a real physical bit that we output and
> wire
> > > back into a Kanalog Input Bit. We can simply use a KFLOP
> Virtual
> > > Bit. These are designed exactly for this type of purpose.Â
> It
> > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> and
> > > off like a real output bit, but KFLOP can also observe and test like
> an
> > > input. Let's use Virtual Bit #48.Â
> > > >
> > > >
> > > > Do you know how to configure an output bit in the Mach3 Config |
> > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> the
> > > Mach3 Macro?
> > > >
> > > > I've uploaded a V5 that uses bit48 to change modes.
> > > >
> > > > Let me know how much of this makes sense.
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >
> > > > Â
> > > > Hi Tom
> > > >
> > > > I will try it tomorrow
> > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> the
> > > torch  on.
> > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > All this can happen in the same G31 macro.
> > > > We use this output for a kanalog input and use it as the Â
> Â
> > > // Plasma is on switch, remove Z from System to allow THC
> > > > Â Â Â Â Â Â Â
> DefineCoordSystem(0,1,-1,-1);
> > > >
> > > > make this sense?
> > > > regards,
> > > > Cees
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > >
> > > > > Hi Cees,
> > > > >
> > > > > I think you are correct. The way we are now has the Z axis
> > > being driven both by the GCode Coordinated Motion System and the THC
> > > Jogs. This is basically like telling the motor to go to two
> > > different
> > > > > places at the same time.
> > > > >
> > > > > I think we require two modes of operation. The Z axis can
> be
> > > added and removed from GCode control with the statements shown
> below:
> > > > >
> > > > >
> > > > > Â Â Â Â Â Â Â Â Â // Plasma is on
> > > switch, remove Z from System to allow THC
> > > > > Â Â Â Â Â Â Â Â Â
> > > DefineCoordSystem(0,1,-1,-1);
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Â Â Â Â Â Â Â Â Â // Plasma is off
> > > switch to normal Z mode
> > > > > Â Â Â Â Â Â Â Â Â
> > > DefineCoordSystem(0,1,2,-1);
> > > > >
> > > > >
> > > > >
> > > > > It just isn't clear to me what signal we should use to switch
> > > modes. Let's try using the Torch ON signal coming from the
> > > unit. Although it isn't totally clear to me what that is.Â
> Does
> > > that indicate that the arc is turned on? Or that the arc is
> > > ready? Maybe it would be better to have a separate bit that we
> can
> > > switch independently of all that? Anyway let's try using the
> Torch
> > > ON signal. I've modified the C program as V4 and uploaded
> it.Â
> > > Please give it a try.
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim atmolgers@
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >
> > > > > Â
> > > > > Hi Tom
> > > > >
> > > > > On the torchmate plasmacutter  sitedriver  they
> explain
> > > how the driver for the plasma cutter works.
> > > > > They speak about X and Y movements and never about the Z
> movement, I
> > > think the Z movement is totally  out of the cooordinate system.
> > > > > I think it is moved by the G31 macro and then by the THC.
> > > > >
> > > > > what do you think?
> > > > >
> > > > > Cees
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6046 From: Tom Kerekes Date: 11/12/2012
Subject: Re: torch height control in Mach
Cees,

Excellent!  Are the files you uploaded to your folder the working ones?

Regards
TK

Group: DynoMotion Message: 6048 From: zeeschuim Date: 11/12/2012
Subject: Re: torch height control in Mach
Yes!

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Cees,
>
> Excellent!  Are the files you uploaded to your folder the working ones?
>
> Regards
> TK
>
>
>
> ________________________________
> From: zeeschuim <atmolgers@...>
> To: DynoMotion@yahoogroups.com
> Sent: Monday, November 12, 2012 8:36 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> All the progams are working!
> Only I have to tame the Polish THC
> It is going like a drunken sailor!
>
> Thanks for the help!
> Cees
>
>
> --- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@> wrote:
> >
> > Never try to close an output 10With a macro M14 what is telling to do"
> > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > regards,Cees
> >
> > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > >
> > > I don't know it anymore
> > >
> > >
> > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > >
> > > > Hi Tom
> > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > close
> > > > this pin 48 output, the torch on/of bit can be used?
> > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > Moves+---------------------------------------------------begin
> > > > PLUNGE_MOVE
> > > > "M15" // this the G31 macro to measure the top of the material, go
> > to
> > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > 1)
> > > > then cutting with THcontrol
> > > > torch of bit wil close pin48 and // Plasma is off switch to normal
> > Z
> > > > mode
> > > > DefineCoordSystem(0,1,2,-1);
> > > > this should be ok, don't you think?
> > > > regards,Cees
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Cees,
> > > > >
> > > > > If I understand you correctly. Using Torch On to switch modes
> > > > will not work, because after the Torch is switched on we still need
> > to
> > > > move Z to the 1.5mm height from GCode. So we need a different
> > > > command (or bit) other than Torch On to switch modes.
> > > > >
> > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > change
> > > > modes. We don't need a real physical bit that we output and
> > wire
> > > > back into a Kanalog Input Bit. We can simply use a KFLOP
> > Virtual
> > > > Bit. These are designed exactly for this type of purpose.Â
> > It
> > > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> > and
> > > > off like a real output bit, but KFLOP can also observe and test like
> > an
> > > > input. Let's use Virtual Bit #48.Â
> > > > >
> > > > >
> > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > the
> > > > Mach3 Macro?
> > > > >
> > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > >
> > > > > Let me know how much of this makes sense.
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim atmolgers@
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >
> > > > > Â
> > > > > Hi Tom
> > > > >
> > > > > I will try it tomorrow
> > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> > the
> > > > torch  on.
> > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > All this can happen in the same G31 macro.
> > > > > We use this output for a kanalog input and use it as the Â
> > Â
> > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > Â Â Â Â Â Â Â
> > DefineCoordSystem(0,1,-1,-1);
> > > > >
> > > > > make this sense?
> > > > > regards,
> > > > > Cees
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > >
> > > > > > Hi Cees,
> > > > > >
> > > > > > I think you are correct. The way we are now has the Z axis
> > > > being driven both by the GCode Coordinated Motion System and the THC
> > > > Jogs. This is basically like telling the motor to go to two
> > > > different
> > > > > > places at the same time.
> > > > > >
> > > > > > I think we require two modes of operation. The Z axis can
> > be
> > > > added and removed from GCode control with the statements shown
> > below:
> > > > > >
> > > > > >
> > > > > > Â Â Â Â Â Â Â Â Â // Plasma is on
> > > > switch, remove Z from System to allow THC
> > > > > > Â Â Â Â Â Â Â Â Â
> > > > DefineCoordSystem(0,1,-1,-1);
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Â Â Â Â Â Â Â Â Â // Plasma is off
> > > > switch to normal Z mode
> > > > > > Â Â Â Â Â Â Â Â Â
> > > > DefineCoordSystem(0,1,2,-1);
> > > > > >
> > > > > >
> > > > > >
> > > > > > It just isn't clear to me what signal we should use to switch
> > > > modes. Let's try using the Torch ON signal coming from the
> > > > unit. Although it isn't totally clear to me what that is.Â
> > Does
> > > > that indicate that the arc is turned on? Or that the arc is
> > > > ready? Maybe it would be better to have a separate bit that we
> > can
> > > > switch independently of all that? Anyway let's try using the
> > Torch
> > > > ON signal. I've modified the C program as V4 and uploaded
> > it.Â
> > > > Please give it a try.
> > > > > >
> > > > > > Regards
> > > > > > TK
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: zeeschuim atmolgers@
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > >
> > > > > >
> > > > > > Â
> > > > > > Hi Tom
> > > > > >
> > > > > > On the torchmate plasmacutter  sitedriver  they
> > explain
> > > > how the driver for the plasma cutter works.
> > > > > > They speak about X and Y movements and never about the Z
> > movement, I
> > > > think the Z movement is totally  out of the cooordinate system.
> > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > >
> > > > > > what do you think?
> > > > > >
> > > > > > Cees
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6049 From: Bengt Sjoelund Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Cees,

What kind of troubles do you have with the Polish THC?
I am planning to buy one soon and interested to know what you have problems with.

Cheers
Bengt

--- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@...> wrote:
>
> Hi Tom
> All the progams are working!Only I have to tame the Polish THCIt is
> going like a drunken sailor!
> Thanks for the help!Cees
>
> --- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@> wrote:
> >
> > Never try to close an output 10With a macro M14 what is telling to do"
> > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > regards,Cees
> >
> > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > >
> > > I don't know it anymore
> > >
> > >
> > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > >
> > > > Hi Tom
> > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > close
> > > > this pin 48 output, the torch on/of bit can be used?
> > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > Moves+---------------------------------------------------begin
> > > > PLUNGE_MOVE
> > > > "M15" // this the G31 macro to measure the top of the material,
> go
> > to
> > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > 1)
> > > > then cutting with THcontrol
> > > > torch of bit wil close pin48 and // Plasma is off switch to
> normal
> > Z
> > > > mode
> > > > DefineCoordSystem(0,1,2,-1);
> > > > this should be ok, don't you think?
> > > > regards,Cees
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Cees,
> > > > >
> > > > > If I understand you correctly. Using Torch On to switch
> modes
> > > > will not work, because after the Torch is switched on we still
> need
> > to
> > > > move Z to the 1.5mm height from GCode. So we need a different
> > > > command (or bit) other than Torch On to switch modes.
> > > > >
> > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > change
> > > > modes. We don't need a real physical bit that we output and
> > wire
> > > > back into a Kanalog Input Bit. We can simply use a KFLOP
> > Virtual
> > > > Bit. These are designed exactly for this type of purpose.Â
> > It
> > > > is like a flag that exists only inside KFLOP that Mach3 can turn
> on
> > and
> > > > off like a real output bit, but KFLOP can also observe and test
> like
> > an
> > > > input. Let's use Virtual Bit #48.Â
> > > > >
> > > > >
> > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > the
> > > > Mach3 Macro?
> > > > >
> > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > >
> > > > > Let me know how much of this makes sense.
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim atmolgers@
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >
> > > > > Â
> > > > > Hi Tom
> > > > >
> > > > > I will try it tomorrow
> > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then
> switch
> > the
> > > > torch  on.
> > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > All this can happen in the same G31 macro.
> > > > > We use this output for a kanalog input and use it as theÂ
> Â
> > Â
> > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > Â Â Â Â Â Â Â
> > DefineCoordSystem(0,1,-1,-1);
> > > > >
> > > > > make this sense?
> > > > > regards,
> > > > > Cees
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > >
> > > > > > Hi Cees,
> > > > > >
> > > > > > I think you are correct. The way we are now has the Z
> axis
> > > > being driven both by the GCode Coordinated Motion System and the
> THC
> > > > Jogs. This is basically like telling the motor to go to two
> > > > different
> > > > > > places at the same time.
> > > > > >
> > > > > > I think we require two modes of operation. The Z axis can
> > be
> > > > added and removed from GCode control with the statements shown
> > below:
> > > > > >
> > > > > >
> > > > > > Â Â Â Â Â Â Â Â Â // Plasma is
> on
> > > > switch, remove Z from System to allow THC
> > > > > > Â Â Â Â Â Â Â Â Â
> > > > DefineCoordSystem(0,1,-1,-1);
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Â Â Â Â Â Â Â Â Â // Plasma is
> off
> > > > switch to normal Z mode
> > > > > > Â Â Â Â Â Â Â Â Â
> > > > DefineCoordSystem(0,1,2,-1);
> > > > > >
> > > > > >
> > > > > >
> > > > > > It just isn't clear to me what signal we should use to switch
> > > > modes. Let's try using the Torch ON signal coming from the
> > > > unit. Although it isn't totally clear to me what that is.Â
> > Does
> > > > that indicate that the arc is turned on? Or that the arc is
> > > > ready? Maybe it would be better to have a separate bit that
> we
> > can
> > > > switch independently of all that? Anyway let's try using the
> > Torch
> > > > ON signal. I've modified the C program as V4 and uploaded
> > it.Â
> > > > Please give it a try.
> > > > > >
> > > > > > Regards
> > > > > > TK
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: zeeschuim atmolgers@
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > >
> > > > > >
> > > > > > Â
> > > > > > Hi Tom
> > > > > >
> > > > > > On the torchmate plasmacutter  sitedriver  they
> > explain
> > > > how the driver for the plasma cutter works.
> > > > > > They speak about X and Y movements and never about the Z
> > movement, I
> > > > think the Z movement is totally  out of the cooordinate
> system.
> > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > >
> > > > > > what do you think?
> > > > > >
> > > > > > Cees
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6050 From: zeeschuim Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Bengt

for now it is not working good
I did send him a message and I have to do some modifications.
I will you know when it is ok
regards,
Cees
--- In DynoMotion@yahoogroups.com, "Bengt Sjoelund" <cnc@...> wrote:
>
> Hi Cees,
>
> What kind of troubles do you have with the Polish THC?
> I am planning to buy one soon and interested to know what you have problems with.
>
> Cheers
> Bengt
>
> --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> >
> > Hi Tom
> > All the progams are working!Only I have to tame the Polish THCIt is
> > going like a drunken sailor!
> > Thanks for the help!Cees
> >
> > --- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@> wrote:
> > >
> > > Never try to close an output 10With a macro M14 what is telling to do"
> > > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > > regards,Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > >
> > > > I don't know it anymore
> > > >
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > >
> > > > > Hi Tom
> > > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > > close
> > > > > this pin 48 output, the torch on/of bit can be used?
> > > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > > Moves+---------------------------------------------------begin
> > > > > PLUNGE_MOVE
> > > > > "M15" // this the G31 macro to measure the top of the material,
> > go
> > > to
> > > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > > 1)
> > > > > then cutting with THcontrol
> > > > > torch of bit wil close pin48 and // Plasma is off switch to
> > normal
> > > Z
> > > > > mode
> > > > > DefineCoordSystem(0,1,2,-1);
> > > > > this should be ok, don't you think?
> > > > > regards,Cees
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > >
> > > > > > Hi Cees,
> > > > > >
> > > > > > If I understand you correctly. Using Torch On to switch
> > modes
> > > > > will not work, because after the Torch is switched on we still
> > need
> > > to
> > > > > move Z to the 1.5mm height from GCode. So we need a different
> > > > > command (or bit) other than Torch On to switch modes.
> > > > > >
> > > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > > change
> > > > > modes. We don't need a real physical bit that we output and
> > > wire
> > > > > back into a Kanalog Input Bit. We can simply use a KFLOP
> > > Virtual
> > > > > Bit. These are designed exactly for this type of purpose.Â
> > > It
> > > > > is like a flag that exists only inside KFLOP that Mach3 can turn
> > on
> > > and
> > > > > off like a real output bit, but KFLOP can also observe and test
> > like
> > > an
> > > > > input. Let's use Virtual Bit #48.Â
> > > > > >
> > > > > >
> > > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > > the
> > > > > Mach3 Macro?
> > > > > >
> > > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > > >
> > > > > > Let me know how much of this makes sense.
> > > > > >
> > > > > > Regards
> > > > > > TK
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: zeeschuim atmolgers@
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > >
> > > > > >
> > > > > > Â
> > > > > > Hi Tom
> > > > > >
> > > > > > I will try it tomorrow
> > > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then
> > switch
> > > the
> > > > > torch  on.
> > > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > > All this can happen in the same G31 macro.
> > > > > > We use this output for a kanalog input and use it as theÂ
> > Â
> > > Â
> > > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > > Â Â Â Â Â Â Â
> > > DefineCoordSystem(0,1,-1,-1);
> > > > > >
> > > > > > make this sense?
> > > > > > regards,
> > > > > > Cees
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > > >
> > > > > > > Hi Cees,
> > > > > > >
> > > > > > > I think you are correct. The way we are now has the Z
> > axis
> > > > > being driven both by the GCode Coordinated Motion System and the
> > THC
> > > > > Jogs. This is basically like telling the motor to go to two
> > > > > different
> > > > > > > places at the same time.
> > > > > > >
> > > > > > > I think we require two modes of operation. The Z axis can
> > > be
> > > > > added and removed from GCode control with the statements shown
> > > below:
> > > > > > >
> > > > > > >
> > > > > > > Â Â Â Â Â Â Â Â Â // Plasma is
> > on
> > > > > switch, remove Z from System to allow THC
> > > > > > > Â Â Â Â Â Â Â Â Â
> > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Â Â Â Â Â Â Â Â Â // Plasma is
> > off
> > > > > switch to normal Z mode
> > > > > > > Â Â Â Â Â Â Â Â Â
> > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > It just isn't clear to me what signal we should use to switch
> > > > > modes. Let's try using the Torch ON signal coming from the
> > > > > unit. Although it isn't totally clear to me what that is.Â
> > > Does
> > > > > that indicate that the arc is turned on? Or that the arc is
> > > > > ready? Maybe it would be better to have a separate bit that
> > we
> > > can
> > > > > switch independently of all that? Anyway let's try using the
> > > Torch
> > > > > ON signal. I've modified the C program as V4 and uploaded
> > > it.Â
> > > > > Please give it a try.
> > > > > > >
> > > > > > > Regards
> > > > > > > TK
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: zeeschuim atmolgers@
> > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > >
> > > > > > >
> > > > > > > Â
> > > > > > > Hi Tom
> > > > > > >
> > > > > > > On the torchmate plasmacutter  sitedriver  they
> > > explain
> > > > > how the driver for the plasma cutter works.
> > > > > > > They speak about X and Y movements and never about the Z
> > > movement, I
> > > > > think the Z movement is totally  out of the cooordinate
> > system.
> > > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > > >
> > > > > > > what do you think?
> > > > > > >
> > > > > > > Cees
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6052 From: tmday7 Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Tom,
Been reading this thread and curious if KFLOP would be able to handle Torch Height Control of its own?

Troy
Group: DynoMotion Message: 6053 From: zeeschuim Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Tom

Is there a possibility to adjust the speed of the Z axe in THC mode?
According the Polish manufacturer is it maybe to fast.

if (ReadBit(143)) // if plasma is ON?
{

if (ReadBit(142))   //Up?
{
Delay_sec(0.1); // Delay for error filter
Jog(2,10000);           // Axis Z move UP
while (ReadBit(142)) ;
Jog(2,0);       
while (!CheckDone(2))  ;   
}
else if (ReadBit(141)) //DOWN?
{
Delay_sec(0.1); //Delay.
Jog(2,-10000);           // Axis Z move DOWN
while (ReadBit(141)) ;
Jog(2,0);       
while (!CheckDone(2))  ;   
}
}
}
 regards,
Cees
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Cees,
>
> Excellent!  Are the files you uploaded to your folder the working ones?
>
> Regards
> TK
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Monday, November 12, 2012 8:36 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> All the progams are working!
> Only I have to tame the Polish THC
> It is going like a drunken sailor!
>
> Thanks for the help!
> Cees
>
>
> --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> >
> > Never try to close an output 10With a macro M14 what is telling to do"
> > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > regards,Cees
> >
> > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > >
> > > I don't know it anymore
> > >
> > >
> > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > >
> > > > Hi Tom
> > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > close
> > > > this pin 48 output, the torch on/of bit can be used?
> > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > Moves+---------------------------------------------------begin
> > > > PLUNGE_MOVE
> > > > "M15" // this the G31 macro to measure the top of the material, go
> > to
> > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > 1)
> > > > then cutting with THcontrol
> > > > torch of bit wil close pin48 and // Plasma is off switch to normal
> > Z
> > > > mode
> > > > DefineCoordSystem(0,1,2,-1);
> > > > this should be ok, don't you think?
> > > > regards,Cees
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Cees,
> > > > >
> > > > > If I understand you correctly. Using Torch On to switch modes
> > > > will not work, because after the Torch is switched on we still need
> > to
> > > > move Z to the 1.5mm height from GCode. So we need a different
> > > > command (or bit) other than Torch On to switch modes.
> > > > >
> > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > change
> > > > modes. We don't need a real physical bit that we output and
> > wire
> > > > back into a Kanalog Input Bit. We can simply use a KFLOP
> > Virtual
> > > > Bit. These are designed exactly for this type of purpose.Â
> > It
> > > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> > and
> > > > off like a real output bit, but KFLOP can also observe and test like
> > an
> > > > input. Let's use Virtual Bit #48.Â
> > > > >
> > > > >
> > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > the
> > > > Mach3 Macro?
> > > > >
> > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > >
> > > > > Let me know how much of this makes sense.
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim atmolgers@
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >
> > > > > Â
> > > > > Hi Tom
> > > > >
> > > > > I will try it tomorrow
> > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> > the
> > > > torch  on.
> > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > All this can happen in the same G31 macro.
> > > > > We use this output for a kanalog input and use it as the Â
> > Â
> > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > Â Â Â Â Â Â Â
> > DefineCoordSystem(0,1,-1,-1);
> > > > >
> > > > > make this sense?
> > > > > regards,
> > > > > Cees
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > >
> > > > > > Hi Cees,
> > > > > >
> > > > > > I think you are correct. The way we are now has the Z axis
> > > > being driven both by the GCode Coordinated Motion System and the THC
> > > > Jogs. This is basically like telling the motor to go to two
> > > > different
> > > > > > places at the same time.
> > > > > >
> > > > > > I think we require two modes of operation. The Z axis can
> > be
> > > > added and removed from GCode control with the statements shown
> > below:
> > > > > >
> > > > > >
> > > > > > Â Â Â Â Â Â Â Â Â // Plasma is on
> > > > switch, remove Z from System to allow THC
> > > > > > Â Â Â Â Â Â Â Â Â
> > > > DefineCoordSystem(0,1,-1,-1);
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Â Â Â Â Â Â Â Â Â // Plasma is off
> > > > switch to normal Z mode
> > > > > > Â Â Â Â Â Â Â Â Â
> > > > DefineCoordSystem(0,1,2,-1);
> > > > > >
> > > > > >
> > > > > >
> > > > > > It just isn't clear to me what signal we should use to switch
> > > > modes. Let's try using the Torch ON signal coming from the
> > > > unit. Although it isn't totally clear to me what that is.Â
> > Does
> > > > that indicate that the arc is turned on? Or that the arc is
> > > > ready? Maybe it would be better to have a separate bit that we
> > can
> > > > switch independently of all that? Anyway let's try using the
> > Torch
> > > > ON signal. I've modified the C program as V4 and uploaded
> > it.Â
> > > > Please give it a try.
> > > > > >
> > > > > > Regards
> > > > > > TK
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: zeeschuim atmolgers@
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > >
> > > > > >
> > > > > > Â
> > > > > > Hi Tom
> > > > > >
> > > > > > On the torchmate plasmacutter  sitedriver  they
> > explain
> > > > how the driver for the plasma cutter works.
> > > > > > They speak about X and Y movements and never about the Z
> > movement, I
> > > > think the Z movement is totally  out of the cooordinate system.
> > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > >
> > > > > > what do you think?
> > > > > >
> > > > > > Cees
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6055 From: zeeschuim Date: 11/13/2012
Subject: Re: torch height control in Mach
something like this?
{
Delay_sec(0.1); // Delay for error filter
ch2->Vel=4000;
Jog(2,10000);           // Axis Z move UP
while (ReadBit(142)) ;
Jog(2,0);       
while (!CheckDone(2))  ;   
}
else if (ReadBit(141)) //DOWN?
{
Delay_sec(0.1); //Delay.
ch2->Vel=4000;
Jog(2,-10000);           // Axis Z move DOWN
while (ReadBit(141)) ;
Jog(2,0);       
while (!CheckDone(2))  ;   
}

regards,
Cees


--- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@...> wrote:
>
> Hi Tom
> Is there a possibility to adjust the speed of the Z axe in THC
> mode?According the Polish manufacturer is it maybe to fast.
> if (ReadBit(143)) // if plasma is ON? {
> if (ReadBit(142)) //Up? { Delay_sec(0.1); // Delay for error
> filter Jog(2,10000); // Axis Z move UP while
> (ReadBit(142)) ; Jog(2,0); while (!CheckDone(2)) ;
> } else if (ReadBit(141)) //DOWN? { Delay_sec(0.1); //Delay.
> Jog(2,-10000); // Axis Z move DOWN while (ReadBit(141)) ;
> Jog(2,0); while (!CheckDone(2)) ; } } }
> regards,Cees
> --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> >
> > Cees,
> >
> > Excellent! Are the files you uploaded to your folder the working
> ones?
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Monday, November 12, 2012 8:36 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> > Â
> > Hi Tom
> >
> > All the progams are working!
> > Only I have to tame the Polish THC
> > It is going like a drunken sailor!
> >
> > Thanks for the help!
> > Cees
> >
> >
> > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > >
> > > Never try to close an output 10With a macro M14 what is telling to
> do"
> > > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > > regards,Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > >
> > > > I don't know it anymore
> > > >
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > >
> > > > > Hi Tom
> > > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > > close
> > > > > this pin 48 output, the torch on/of bit can be used?
> > > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > > Moves+---------------------------------------------------begin
> > > > > PLUNGE_MOVE
> > > > > "M15" // this the G31 macro to measure the top of the
> material, go
> > > to
> > > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48
> port
> > > 1)
> > > > > then cutting with THcontrol
> > > > > torch of bit wil close pin48 and // Plasma is off switch to
> normal
> > > Z
> > > > > mode
> > > > > DefineCoordSystem(0,1,2,-1);
> > > > > this should be ok, don't you think?
> > > > > regards,Cees
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > >
> > > > > > Hi Cees,
> > > > > >
> > > > > > If I understand you correctly. Using Torch On to switch
> modes
> > > > > will not work, because after the Torch is switched on we still
> need
> > > to
> > > > > move Z to the 1.5mm height from GCode. So we need a
> different
> > > > > command (or bit) other than Torch On to switch modes.
> > > > > >
> > > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > > change
> > > > > modes. We don't need a real physical bit that we output
> and
> > > wire
> > > > > back into a Kanalog Input Bit. We can simply use a KFLOP
> > > Virtual
> > > > > Bit. These are designed exactly for this type of
> purpose.Â
> > > It
> > > > > is like a flag that exists only inside KFLOP that Mach3 can turn
> on
> > > and
> > > > > off like a real output bit, but KFLOP can also observe and test
> like
> > > an
> > > > > input. Let's use Virtual Bit #48.Â
> > > > > >
> > > > > >
> > > > > > Do you know how to configure an output bit in the Mach3 Config
> |
> > > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on
> from
> > > the
> > > > > Mach3 Macro?
> > > > > >
> > > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > > >
> > > > > > Let me know how much of this makes sense.
> > > > > >
> > > > > > Regards
> > > > > > TK
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: zeeschuim atmolgers@
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > >
> > > > > >
> > > > > > Â
> > > > > > Hi Tom
> > > > > >
> > > > > > I will try it tomorrow
> > > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then
> switch
> > > the
> > > > > torch  on.
> > > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > > All this can happen in the same G31 macro.
> > > > > > We use this output for a kanalog input and use it as theÂ
> Â
> > > Â
> > > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > > Â Â Â Â Â Â Â
> > > DefineCoordSystem(0,1,-1,-1);
> > > > > >
> > > > > > make this sense?
> > > > > > regards,
> > > > > > Cees
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > > >
> > > > > > > Hi Cees,
> > > > > > >
> > > > > > > I think you are correct. The way we are now has the Z
> axis
> > > > > being driven both by the GCode Coordinated Motion System and the
> THC
> > > > > Jogs. This is basically like telling the motor to go to
> two
> > > > > different
> > > > > > > places at the same time.
> > > > > > >
> > > > > > > I think we require two modes of operation. The Z axis
> can
> > > be
> > > > > added and removed from GCode control with the statements shown
> > > below:
> > > > > > >
> > > > > > >
> > > > > > > Â Â Â Â Â Â Â Â
> Â // Plasma is on
> > > > > switch, remove Z from System to allow THC
> > > > > > > Â Â Â Â Â Â Â Â
> Â
> > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Â Â Â Â Â Â Â Â
> Â // Plasma is off
> > > > > switch to normal Z mode
> > > > > > > Â Â Â Â Â Â Â Â
> Â
> > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > It just isn't clear to me what signal we should use to
> switch
> > > > > modes. Let's try using the Torch ON signal coming from
> the
> > > > > unit. Although it isn't totally clear to me what that
> is.Â
> > > Does
> > > > > that indicate that the arc is turned on? Or that the arc
> is
> > > > > ready? Maybe it would be better to have a separate bit
> that we
> > > can
> > > > > switch independently of all that? Anyway let's try using
> the
> > > Torch
> > > > > ON signal. I've modified the C program as V4 and uploaded
> > > it.Â
> > > > > Please give it a try.
> > > > > > >
> > > > > > > Regards
> > > > > > > TK
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: zeeschuim atmolgers@
> > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > >
> > > > > > >
> > > > > > > Â
> > > > > > > Hi Tom
> > > > > > >
> > > > > > > On the torchmate plasmacutter  sitedriver Â
> they
> > > explain
> > > > > how the driver for the plasma cutter works.
> > > > > > > They speak about X and Y movements and never about the Z
> > > movement, I
> > > > > think the Z movement is totally  out of the cooordinate
> system.
> > > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > > >
> > > > > > > what do you think?
> > > > > > >
> > > > > > > Cees
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6057 From: Tom Kerekes Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Troy,

Not sure what you mean by "of its own".  But yes I think a number of users have fed in the Torch Voltage or Current into Kanalog (of course after conditioning it to a 0-10V signal) and created a dual loop servo.  This should work better because rather than simply getting up/down commands like Cees receives, the servo knows the amount of error so it can control the correction speed proportionally and so forth.  It also allows plotting and tuning the loop to make corrections in the optimal manner.

Regards
TK


Group: DynoMotion Message: 6058 From: Tom Kerekes Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Cees,

Certainly.  Change the Jog Speeds.  (they are the 10000 and -10000 steps per second)

Regards
TK

Group: DynoMotion Message: 6059 From: zeeschuim Date: 11/13/2012
Subject: Re: torch height control in Mach
Ok
I thought they were the distances.
Can the distance also be done?

regards,
Cees

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> Certainly.  Change the Jog Speeds.  (they are the 10000 and -10000 steps per second)
>
> Regards
> TK
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, November 13, 2012 7:48 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> Is there a possibility to adjust the speed of the Z axe in THC mode?
> According the Polish manufacturer is it maybe to fast.
>
> if (ReadBit(143)) // if plasma is ON?
> {
>
> if (ReadBit(142))   //Up?
> {
> Delay_sec(0.1); // Delay for error filter
> Jog(2,10000);           // Axis Z move UP
> while (ReadBit(142)) ;
> Jog(2,0);       
> while (!CheckDone(2))  ;   
> }
> else if (ReadBit(141)) //DOWN?
> {
> Delay_sec(0.1); //Delay.
> Jog(2,-10000);           // Axis Z move DOWN
> while (ReadBit(141)) ;
> Jog(2,0);       
> while (!CheckDone(2))  ;   
> }
> }
> }
>  regards,
> Cees
> --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> >
> > Cees,
> >
> > Excellent!  Are the files you uploaded to your folder the working ones?
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Monday, November 12, 2012 8:36 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > Hi Tom
> >
> > All the progams are working!
> > Only I have to tame the Polish THC
> > It is going like a drunken sailor!
> >
> > Thanks for the help!
> > Cees
> >
> >
> > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > >
> > > Never try to close an output 10With a macro M14 what is telling to do"
> > > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > > regards,Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > >
> > > > I don't know it anymore
> > > >
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > >
> > > > > Hi Tom
> > > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > > close
> > > > > this pin 48 output, the torch on/of bit can be used?
> > > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > > Moves+---------------------------------------------------begin
> > > > > PLUNGE_MOVE
> > > > > "M15" // this the G31 macro to measure the top of the material, go
> > > to
> > > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > > 1)
> > > > > then cutting with THcontrol
> > > > > torch of bit wil close pin48 and // Plasma is off switch to normal
> > > Z
> > > > > mode
> > > > > DefineCoordSystem(0,1,2,-1);
> > > > > this should be ok, don't you think?
> > > > > regards,Cees
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > >
> > > > > > Hi Cees,
> > > > > >
> > > > > > If I understand you correctly. Using Torch On to switch modes
> > > > > will not work, because after the Torch is switched on we still need
> > > to
> > > > > move Z to the 1.5mm height from GCode. So we need a different
> > > > > command (or bit) other than Torch On to switch modes.
> > > > > >
> > > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > > change
> > > > > modes. We don't need a real physical bit that we output and
> > > wire
> > > > > back into a Kanalog Input Bit. We can simply use a KFLOP
> > > Virtual
> > > > > Bit. These are designed exactly for this type of purpose.Â
> > > It
> > > > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> > > and
> > > > > off like a real output bit, but KFLOP can also observe and test like
> > > an
> > > > > input. Let's use Virtual Bit #48.Â
> > > > > >
> > > > > >
> > > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > > the
> > > > > Mach3 Macro?
> > > > > >
> > > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > > >
> > > > > > Let me know how much of this makes sense.
> > > > > >
> > > > > > Regards
> > > > > > TK
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: zeeschuim atmolgers@
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > >
> > > > > >
> > > > > > Â
> > > > > > Hi Tom
> > > > > >
> > > > > > I will try it tomorrow
> > > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> > > the
> > > > > torch  on.
> > > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > > All this can happen in the same G31 macro.
> > > > > > We use this output for a kanalog input and use it as the Â
> > > Â
> > > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > > Â Â Â Â Â Â Â
> > > DefineCoordSystem(0,1,-1,-1);
> > > > > >
> > > > > > make this sense?
> > > > > > regards,
> > > > > > Cees
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > > >
> > > > > > > Hi Cees,
> > > > > > >
> > > > > > > I think you are correct. The way we are now has the Z axis
> > > > > being driven both by the GCode Coordinated Motion System and the THC
> > > > > Jogs. This is basically like telling the motor to go to two
> > > > > different
> > > > > > > places at the same time.
> > > > > > >
> > > > > > > I think we require two modes of operation. The Z axis can
> > > be
> > > > > added and removed from GCode control with the statements shown
> > > below:
> > > > > > >
> > > > > > >
> > > > > > > Â Â Â Â Â Â Â Â Â // Plasma is on
> > > > > switch, remove Z from System to allow THC
> > > > > > > Â Â Â Â Â Â Â Â Â
> > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Â Â Â Â Â Â Â Â Â // Plasma is off
> > > > > switch to normal Z mode
> > > > > > > Â Â Â Â Â Â Â Â Â
> > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > It just isn't clear to me what signal we should use to switch
> > > > > modes. Let's try using the Torch ON signal coming from the
> > > > > unit. Although it isn't totally clear to me what that is.Â
> > > Does
> > > > > that indicate that the arc is turned on? Or that the arc is
> > > > > ready? Maybe it would be better to have a separate bit that we
> > > can
> > > > > switch independently of all that? Anyway let's try using the
> > > Torch
> > > > > ON signal. I've modified the C program as V4 and uploaded
> > > it.Â
> > > > > Please give it a try.
> > > > > > >
> > > > > > > Regards
> > > > > > > TK
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: zeeschuim atmolgers@
> > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > >
> > > > > > >
> > > > > > > Â
> > > > > > > Hi Tom
> > > > > > >
> > > > > > > On the torchmate plasmacutter  sitedriver  they
> > > explain
> > > > > how the driver for the plasma cutter works.
> > > > > > > They speak about X and Y movements and never about the Z
> > > movement, I
> > > > > think the Z movement is totally  out of the cooordinate system.
> > > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > > >
> > > > > > > what do you think?
> > > > > > >
> > > > > > > Cees
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6060 From: Tom Kerekes Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Cees,

You could issue a MoveRelAtVel instead of a Jog, but I'm not sure that would make sense.  Don't you want to move until it tells you to stop?

The difference is that it would then stop after some distance if never told to stop.  But would do another move if it commanded a stop and then another move.

Regards
TK

Group: DynoMotion Message: 6061 From: zeeschuim Date: 11/13/2012
Subject: Re: torch height control in Mach
ok
sometimes it goes to deep or to hi, it is lost control totally.
But maybe it is the speed.
Now it goes 800mm/min and this is to fast for my THC, I think.
I will change it to 100mm or less.

regards,
Cees


--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> You could issue a MoveRelAtVel instead of a Jog, but I'm not sure that would make sense.  Don't you want to move until it tells you to stop?
>
> The difference is that it would then stop after some distance if never told to stop.  But would do another move if it commanded a stop and then another move.
>
>
> Regards
> TK
>
>
>
> ________________________________
> From: zeeschuim <atmolgers@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, November 13, 2012 12:02 PM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Ok
> I thought they were the distances.
> Can the distance also be done?
>
> regards,
> Cees
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Cees,
> >
> > Certainly.  Change the Jog Speeds.  (they are the 10000 and -10000 steps per second)
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, November 13, 2012 7:48 AM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > Hi Tom
> >
> > Is there a possibility to adjust the speed of the Z axe in THC mode?
> > According the Polish manufacturer is it maybe to fast.
> >
> > if (ReadBit(143)) // if plasma is ON?
> > {
> >
> > if (ReadBit(142))   //Up?
> > {
> > Delay_sec(0.1); // Delay for error filter
> > Jog(2,10000);           // Axis Z move UP
> > while (ReadBit(142)) ;
> > Jog(2,0);       
> > while (!CheckDone(2))  ;   
> > }
> > else if (ReadBit(141)) //DOWN?
> > {
> > Delay_sec(0.1); //Delay.
> > Jog(2,-10000);           // Axis Z move DOWN
> > while (ReadBit(141)) ;
> > Jog(2,0);       
> > while (!CheckDone(2))  ;   
> > }
> > }
> > }
> >  regards,
> > Cees
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > >
> > > Cees,
> > >
> > > Excellent!  Are the files you uploaded to your folder the working ones?
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim atmolgers@
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Monday, November 12, 2012 8:36 AM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > >  
> > > Hi Tom
> > >
> > > All the progams are working!
> > > Only I have to tame the Polish THC
> > > It is going like a drunken sailor!
> > >
> > > Thanks for the help!
> > > Cees
> > >
> > >
> > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > >
> > > > Never try to close an output 10With a macro M14 what is telling to do"
> > > > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > > > regards,Cees
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > >
> > > > > I don't know it anymore
> > > > >
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > >
> > > > > > Hi Tom
> > > > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > > > close
> > > > > > this pin 48 output, the torch on/of bit can be used?
> > > > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > > > Moves+---------------------------------------------------begin
> > > > > > PLUNGE_MOVE
> > > > > > "M15" // this the G31 macro to measure the top of the material, go
> > > > to
> > > > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > > > 1)
> > > > > > then cutting with THcontrol
> > > > > > torch of bit wil close pin48 and // Plasma is off switch to normal
> > > > Z
> > > > > > mode
> > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > this should be ok, don't you think?
> > > > > > regards,Cees
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > >
> > > > > > > Hi Cees,
> > > > > > >
> > > > > > > If I understand you correctly.ÃÆ'‚ Using Torch On to switch modes
> > > > > > will not work, because after the Torch is switched on we still need
> > > > to
> > > > > > move Z to the 1.5mm height from GCode.ÃÆ'‚ So we need a different
> > > > > > command (or bit) other than Torch On to switch modes.
> > > > > > >
> > > > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > > > change
> > > > > > modes.ÃÆ'‚ We don't need a real physical bit that we output and
> > > > wire
> > > > > > back into a Kanalog Input Bit.ÃÆ'‚ We can simply use a KFLOP
> > > > Virtual
> > > > > > Bit.ÃÆ'‚ These are designed exactly for this type of purpose.ÃÆ'‚
> > > > It
> > > > > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> > > > and
> > > > > > off like a real output bit, but KFLOP can also observe and test like
> > > > an
> > > > > > input.ÃÆ'‚ Let's use Virtual Bit #48.ÃÆ'‚
> > > > > > >
> > > > > > >
> > > > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > > > the
> > > > > > Mach3 Macro?
> > > > > > >
> > > > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > > > >
> > > > > > > Let me know how much of this makes sense.
> > > > > > >
> > > > > > > Regards
> > > > > > > TK
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: zeeschuim atmolgers@
> > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > >
> > > > > > >
> > > > > > > ÃÆ'‚
> > > > > > > Hi Tom
> > > > > > >
> > > > > > > I will try it tomorrow
> > > > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> > > > the
> > > > > > torch ÃÆ'‚ on.
> > > > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > > > All this can happen in the same G31 macro.
> > > > > > > We use this output for a kanalog input and use it as theÃÆ'‚ ÃÆ'‚
> > > > ÃÆ'‚
> > > > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > > > ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚
> > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > >
> > > > > > > make this sense?
> > > > > > > regards,
> > > > > > > Cees
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > > > >
> > > > > > > > Hi Cees,
> > > > > > > >
> > > > > > > > I think you are correct.ÃÆ'‚ The way we are now has the Z axis
> > > > > > being driven both by the GCode Coordinated Motion System and the THC
> > > > > > Jogs.ÃÆ'‚ This is basically like telling the motor to go to two
> > > > > > different
> > > > > > > > places at the same time.
> > > > > > > >
> > > > > > > > I think we require two modes of operation.ÃÆ'‚ The Z axis can
> > > > be
> > > > > > added and removed from GCode control with the statements shown
> > > > below:
> > > > > > > >
> > > > > > > >
> > > > > > > > ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ // Plasma is on
> > > > > > switch, remove Z from System to allow THC
> > > > > > > > ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚
> > > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ // Plasma is off
> > > > > > switch to normal Z mode
> > > > > > > > ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚ ÃÆ'‚
> > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > It just isn't clear to me what signal we should use to switch
> > > > > > modes.ÃÆ'‚ Let's try using the Torch ON signal coming from the
> > > > > > unit.ÃÆ'‚ Although it isn't totally clear to me what that is.ÃÆ'‚
> > > > Does
> > > > > > that indicate that the arc is turned on?ÃÆ'‚ Or that the arc is
> > > > > > ready?ÃÆ'‚ Maybe it would be better to have a separate bit that we
> > > > can
> > > > > > switch independently of all that?ÃÆ'‚ Anyway let's try using the
> > > > Torch
> > > > > > ON signal.ÃÆ'‚ I've modified the C program as V4 and uploaded
> > > > it.ÃÆ'‚
> > > > > > Please give it a try.
> > > > > > > >
> > > > > > > > Regards
> > > > > > > > TK
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ________________________________
> > > > > > > > From: zeeschuim atmolgers@
> > > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > >
> > > > > > > >
> > > > > > > > ÃÆ'‚
> > > > > > > > Hi Tom
> > > > > > > >
> > > > > > > > On the torchmate plasmacutter ÃÆ'‚ sitedriverÃÆ'‚ ÃÆ'‚ they
> > > > explain
> > > > > > how the driver for the plasma cutter works.
> > > > > > > > They speak about X and Y movements and never about the Z
> > > > movement, I
> > > > > > think the Z movement is totally ÃÆ'‚ out of the cooordinate system.
> > > > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > > > >
> > > > > > > > what do you think?
> > > > > > > >
> > > > > > > > Cees
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6062 From: Tom Kerekes Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Cees,

ok. You might want to have the program to remember the z height when the THC ON first comes on.  Then disallow motion if z ever tries to move too far from that starting position.  But if your panels have a lot of curvature that wouldn't really help.

I've heard Users mention "anti-dive" methods.  But I don't know what that is exactly. 

Regards
TK

Group: DynoMotion Message: 6063 From: zeeschuim Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Tom

In the Mach3 plasma screenset, there are two DRO's for the max height and the Min. height.
Or something in machine coordinates?

regards,
Cees

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> ok. You might want to have the program to remember the z height when the THC ON first comes on.  Then disallow motion if z ever tries to move too far from that starting position.  But if your panels have a lot of curvature that wouldn't really help.
>
> I've heard Users mention "anti-dive" methods.  But I don't know what that is exactly. 
>
>
> Regards
> TK
>
>
>
> ________________________________
> From: zeeschuim <atmolgers@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, November 13, 2012 12:44 PM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> ok
> sometimes it goes to deep or to hi, it is lost control totally.
> But maybe it is the speed.
> Now it goes 800mm/min and this is to fast for my THC, I think.
> I will change it to 100mm or less.
>
> regards,
> Cees
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Cees,
> >
> > You could issue a MoveRelAtVel instead of a Jog, but I'm not sure that would make sense.  Don't you want to move until it tells you to stop?
> >
> > The difference is that it would then stop after some distance if never told to stop.  But would do another move if it commanded a stop and then another move.
> >
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: zeeschuim <atmolgers@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, November 13, 2012 12:02 PM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > Ok
> > I thought they were the distances.
> > Can the distance also be done?
> >
> > regards,
> > Cees
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Cees,
> > >
> > > Certainly.  Change the Jog Speeds.  (they are the 10000 and -10000 steps per second)
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim atmolgers@
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Tuesday, November 13, 2012 7:48 AM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > >  
> > > Hi Tom
> > >
> > > Is there a possibility to adjust the speed of the Z axe in THC mode?
> > > According the Polish manufacturer is it maybe to fast.
> > >
> > > if (ReadBit(143)) // if plasma is ON?
> > > {
> > >
> > > if (ReadBit(142))   //Up?
> > > {
> > > Delay_sec(0.1); // Delay for error filter
> > > Jog(2,10000);           // Axis Z move UP
> > > while (ReadBit(142)) ;
> > > Jog(2,0);       
> > > while (!CheckDone(2))  ;   
> > > }
> > > else if (ReadBit(141)) //DOWN?
> > > {
> > > Delay_sec(0.1); //Delay.
> > > Jog(2,-10000);           // Axis Z move DOWN
> > > while (ReadBit(141)) ;
> > > Jog(2,0);       
> > > while (!CheckDone(2))  ;   
> > > }
> > > }
> > > }
> > >  regards,
> > > Cees
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > >
> > > > Cees,
> > > >
> > > > Excellent!ÃÆ'‚  Are the files you uploaded to your folder the working ones?
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Monday, November 12, 2012 8:36 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >
> > > > ÃÆ'‚ 
> > > > Hi Tom
> > > >
> > > > All the progams are working!
> > > > Only I have to tame the Polish THC
> > > > It is going like a drunken sailor!
> > > >
> > > > Thanks for the help!
> > > > Cees
> > > >
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > >
> > > > > Never try to close an output 10With a macro M14 what is telling to do"
> > > > > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > > > > regards,Cees
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > >
> > > > > > I don't know it anymore
> > > > > >
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > > >
> > > > > > > Hi Tom
> > > > > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > > > > close
> > > > > > > this pin 48 output, the torch on/of bit can be used?
> > > > > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > > > > Moves+---------------------------------------------------begin
> > > > > > > PLUNGE_MOVE
> > > > > > > "M15" // this the G31 macro to measure the top of the material, go
> > > > > to
> > > > > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > > > > 1)
> > > > > > > then cutting with THcontrol
> > > > > > > torch of bit wil close pin48 and // Plasma is off switch to normal
> > > > > Z
> > > > > > > mode
> > > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > > this should be ok, don't you think?
> > > > > > > regards,Cees
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > > >
> > > > > > > > Hi Cees,
> > > > > > > >
> > > > > > > > If I understand you correctly.ÃÆ'Æ'‚ Using Torch On to switch modes
> > > > > > > will not work, because after the Torch is switched on we still need
> > > > > to
> > > > > > > move Z to the 1.5mm height from GCode.ÃÆ'Æ'‚ So we need a different
> > > > > > > command (or bit) other than Torch On to switch modes.
> > > > > > > >
> > > > > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > > > > change
> > > > > > > modes.ÃÆ'Æ'‚ We don't need a real physical bit that we output and
> > > > > wire
> > > > > > > back into a Kanalog Input Bit.ÃÆ'Æ'‚ We can simply use a KFLOP
> > > > > Virtual
> > > > > > > Bit.ÃÆ'Æ'‚ These are designed exactly for this type of purpose.ÃÆ'Æ'‚
> > > > > It
> > > > > > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> > > > > and
> > > > > > > off like a real output bit, but KFLOP can also observe and test like
> > > > > an
> > > > > > > input.ÃÆ'Æ'‚ Let's use Virtual Bit #48.ÃÆ'Æ'‚
> > > > > > > >
> > > > > > > >
> > > > > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > > > > the
> > > > > > > Mach3 Macro?
> > > > > > > >
> > > > > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > > > > >
> > > > > > > > Let me know how much of this makes sense.
> > > > > > > >
> > > > > > > > Regards
> > > > > > > > TK
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ________________________________
> > > > > > > > From: zeeschuim atmolgers@
> > > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > >
> > > > > > > >
> > > > > > > > ÃÆ'Æ'‚
> > > > > > > > Hi Tom
> > > > > > > >
> > > > > > > > I will try it tomorrow
> > > > > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> > > > > the
> > > > > > > torch ÃÆ'Æ'‚ on.
> > > > > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > > > > All this can happen in the same G31 macro.
> > > > > > > > We use this output for a kanalog input and use it as theÃÆ'Æ'‚ ÃÆ'Æ'‚
> > > > > ÃÆ'Æ'‚
> > > > > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > > > > ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚
> > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > > >
> > > > > > > > make this sense?
> > > > > > > > regards,
> > > > > > > > Cees
> > > > > > > >
> > > > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > > > > >
> > > > > > > > > Hi Cees,
> > > > > > > > >
> > > > > > > > > I think you are correct.ÃÆ'Æ'‚ The way we are now has the Z axis
> > > > > > > being driven both by the GCode Coordinated Motion System and the THC
> > > > > > > Jogs.ÃÆ'Æ'‚ This is basically like telling the motor to go to two
> > > > > > > different
> > > > > > > > > places at the same time.
> > > > > > > > >
> > > > > > > > > I think we require two modes of operation.ÃÆ'Æ'‚ The Z axis can
> > > > > be
> > > > > > > added and removed from GCode control with the statements shown
> > > > > below:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ // Plasma is on
> > > > > > > switch, remove Z from System to allow THC
> > > > > > > > > ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚
> > > > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ // Plasma is off
> > > > > > > switch to normal Z mode
> > > > > > > > > ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚ ÃÆ'Æ'‚
> > > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > It just isn't clear to me what signal we should use to switch
> > > > > > > modes.ÃÆ'Æ'‚ Let's try using the Torch ON signal coming from the
> > > > > > > unit.ÃÆ'Æ'‚ Although it isn't totally clear to me what that is.ÃÆ'Æ'‚
> > > > > Does
> > > > > > > that indicate that the arc is turned on?ÃÆ'Æ'‚ Or that the arc is
> > > > > > > ready?ÃÆ'Æ'‚ Maybe it would be better to have a separate bit that we
> > > > > can
> > > > > > > switch independently of all that?ÃÆ'Æ'‚ Anyway let's try using the
> > > > > Torch
> > > > > > > ON signal.ÃÆ'Æ'‚ I've modified the C program as V4 and uploaded
> > > > > it.ÃÆ'Æ'‚
> > > > > > > Please give it a try.
> > > > > > > > >
> > > > > > > > > Regards
> > > > > > > > > TK
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ________________________________
> > > > > > > > > From: zeeschuim atmolgers@
> > > > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ÃÆ'Æ'‚
> > > > > > > > > Hi Tom
> > > > > > > > >
> > > > > > > > > On the torchmate plasmacutter ÃÆ'Æ'‚ sitedriverÃÆ'Æ'‚ ÃÆ'Æ'‚ they
> > > > > explain
> > > > > > > how the driver for the plasma cutter works.
> > > > > > > > > They speak about X and Y movements and never about the Z
> > > > > movement, I
> > > > > > > think the Z movement is totally ÃÆ'Æ'‚ out of the cooordinate system.
> > > > > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > > > > >
> > > > > > > > > what do you think?
> > > > > > > > >
> > > > > > > > > Cees
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6065 From: Tom Kerekes Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Cees,

If you found out what those actually do we could do something similar like I described.

The obvious problem with setting limits is if for example we start at a height of 5mm and the flatness of your material varies by +/- 10mm then we must allow +/- 10mm of motion so that wouldn't necessarily help crashing.

I Google and found this:

http://www.cnczone.com/forums/mach_plasma_laser/103229-thc_settings_explanation_-_clear.html

And this (ignore THC Up/Down when the xy velocity is slow)

http://www.machsupport.com/forum/index.php?topic=16169.0

We can do anything you wish but you must understand the problem first.

Regards
TK


Group: DynoMotion Message: 6066 From: zeeschuim Date: 11/13/2012
Subject: Re: torch height control in Mach
I will read it

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> If you found out what those actually do we could do something similar like I described.
>
> The obvious problem with setting limits is if for example we start at a height of 5mm and the flatness of your material varies by +/- 10mm then we must allow +/- 10mm of motion so that wouldn't necessarily help crashing.
>
> I Google and found this:
>
> http://www.cnczone.com/forums/mach_plasma_laser/103229-thc_settings_explanation_-_clear.html
>
> And this (ignore THC Up/Down when the xy velocity is slow)
>
> http://www.machsupport.com/forum/index.php?topic=16169.0
>
> We can do anything you wish but you must understand the problem first.
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: zeeschuim <atmolgers@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, November 13, 2012 1:01 PM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> In the Mach3 plasma screenset, there are two DRO's for the max height and the Min. height.
> Or something in machine coordinates?
>
> regards,
> Cees
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Cees,
> >
> > ok. You might want to have the program to remember the z height when the THC ON first comes on.  Then disallow motion if z ever tries to move too far from that starting position.  But if your panels have a lot of curvature that wouldn't really help.
> >
> > I've heard Users mention "anti-dive" methods.  But I don't know what that is exactly. 
> >
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: zeeschuim <atmolgers@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, November 13, 2012 12:44 PM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > ok
> > sometimes it goes to deep or to hi, it is lost control totally.
> > But maybe it is the speed.
> > Now it goes 800mm/min and this is to fast for my THC, I think.
> > I will change it to 100mm or less.
> >
> > regards,
> > Cees
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Cees,
> > >
> > > You could issue a MoveRelAtVel instead of a Jog, but I'm not sure that would make sense.  Don't you want to move until it tells you to stop?
> > >
> > > The difference is that it would then stop after some distance if never told to stop.  But would do another move if it commanded a stop and then another move.
> > >
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim <atmolgers@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Tuesday, November 13, 2012 12:02 PM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > >  
> > > Ok
> > > I thought they were the distances.
> > > Can the distance also be done?
> > >
> > > regards,
> > > Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Cees,
> > > >
> > > > Certainly.ÃÆ'‚  Change the Jog Speeds.ÃÆ'‚  (they are the 10000 and -10000 steps per second)
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Tuesday, November 13, 2012 7:48 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >
> > > > ÃÆ'‚ 
> > > > Hi Tom
> > > >
> > > > Is there aÃÆ'‚ possibility to adjust the speed of the Z axe in THC mode?
> > > > According the PolishÃÆ'‚ manufacturerÃÆ'‚ is it maybe to fast.
> > > >
> > > > if (ReadBit(143)) // if plasma is ON?
> > > > {
> > > >
> > > > if (ReadBit(142)) ÃÆ'‚  //Up?
> > > > {
> > > > Delay_sec(0.1); // Delay for error filter
> > > > Jog(2,10000); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  // Axis Z move UP
> > > > while (ReadBit(142)) ;
> > > > Jog(2,0); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚ ÃÆ'‚ 
> > > > while (!CheckDone(2)) ÃÆ'‚ ; ÃÆ'‚ ÃÆ'‚ 
> > > > }
> > > > else if (ReadBit(141)) //DOWN?
> > > > {
> > > > Delay_sec(0.1); //Delay.
> > > > Jog(2,-10000); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  // Axis Z move DOWN
> > > > while (ReadBit(141)) ;
> > > > Jog(2,0); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚ ÃÆ'‚ 
> > > > while (!CheckDone(2)) ÃÆ'‚ ; ÃÆ'‚ ÃÆ'‚ 
> > > > }
> > > > }
> > > > }
> > > > ÃÆ'‚ regards,
> > > > Cees
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > >
> > > > > Cees,
> > > > >
> > > > > Excellent!ÃÆ'Æ'‚ÃÆ'‚  Are the files you uploaded to your folder the working ones?
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim atmolgers@
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Monday, November 12, 2012 8:36 AM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >
> > > > > ÃÆ'Æ'‚ÃÆ'‚ 
> > > > > Hi Tom
> > > > >
> > > > > All the progams are working!
> > > > > Only I have to tame the Polish THC
> > > > > It is going like a drunken sailor!
> > > > >
> > > > > Thanks for the help!
> > > > > Cees
> > > > >
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > >
> > > > > > Never try to close an output 10With a macro M14 what is telling to do"
> > > > > > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > > > > > regards,Cees
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > > >
> > > > > > > I don't know it anymore
> > > > > > >
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > > > >
> > > > > > > > Hi Tom
> > > > > > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > > > > > close
> > > > > > > > this pin 48 output, the torch on/of bit can be used?
> > > > > > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > > > > > Moves+---------------------------------------------------begin
> > > > > > > > PLUNGE_MOVE
> > > > > > > > "M15" // this the G31 macro to measure the top of the material, go
> > > > > > to
> > > > > > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > > > > > 1)
> > > > > > > > then cutting with THcontrol
> > > > > > > > torch of bit wil close pin48 and // Plasma is off switch to normal
> > > > > > Z
> > > > > > > > mode
> > > > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > > > this should be ok, don't you think?
> > > > > > > > regards,Cees
> > > > > > > >
> > > > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > > > >
> > > > > > > > > Hi Cees,
> > > > > > > > >
> > > > > > > > > If I understand you correctly.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Using Torch On to switch modes
> > > > > > > > will not work, because after the Torch is switched on we still need
> > > > > > to
> > > > > > > > move Z to the 1.5mm height from GCode.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ So we need a different
> > > > > > > > command (or bit) other than Torch On to switch modes.
> > > > > > > > >
> > > > > > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > > > > > change
> > > > > > > > modes.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ We don't need a real physical bit that we output and
> > > > > > wire
> > > > > > > > back into a Kanalog Input Bit.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ We can simply use a KFLOP
> > > > > > Virtual
> > > > > > > > Bit.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ These are designed exactly for this type of purpose.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > It
> > > > > > > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> > > > > > and
> > > > > > > > off like a real output bit, but KFLOP can also observe and test like
> > > > > > an
> > > > > > > > input.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Let's use Virtual Bit #48.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > > > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > > > > > the
> > > > > > > > Mach3 Macro?
> > > > > > > > >
> > > > > > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > > > > > >
> > > > > > > > > Let me know how much of this makes sense.
> > > > > > > > >
> > > > > > > > > Regards
> > > > > > > > > TK
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ________________________________
> > > > > > > > > From: zeeschuim atmolgers@
> > > > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > Hi Tom
> > > > > > > > >
> > > > > > > > > I will try it tomorrow
> > > > > > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> > > > > > the
> > > > > > > > torch ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ on.
> > > > > > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > > > > > All this can happen in the same G31 macro.
> > > > > > > > > We use this output for a kanalog input and use it as theÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > > > >
> > > > > > > > > make this sense?
> > > > > > > > > regards,
> > > > > > > > > Cees
> > > > > > > > >
> > > > > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Cees,
> > > > > > > > > >
> > > > > > > > > > I think you are correct.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ The way we are now has the Z axis
> > > > > > > > being driven both by the GCode Coordinated Motion System and the THC
> > > > > > > > Jogs.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ This is basically like telling the motor to go to two
> > > > > > > > different
> > > > > > > > > > places at the same time.
> > > > > > > > > >
> > > > > > > > > > I think we require two modes of operation.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ The Z axis can
> > > > > > be
> > > > > > > > added and removed from GCode control with the statements shown
> > > > > > below:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ // Plasma is on
> > > > > > > > switch, remove Z from System to allow THC
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ // Plasma is off
> > > > > > > > switch to normal Z mode
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > It just isn't clear to me what signal we should use to switch
> > > > > > > > modes.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Let's try using the Torch ON signal coming from the
> > > > > > > > unit.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Although it isn't totally clear to me what that is.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > Does
> > > > > > > > that indicate that the arc is turned on?ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Or that the arc is
> > > > > > > > ready?ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Maybe it would be better to have a separate bit that we
> > > > > > can
> > > > > > > > switch independently of all that?ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Anyway let's try using the
> > > > > > Torch
> > > > > > > > ON signal.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ I've modified the C program as V4 and uploaded
> > > > > > it.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > Please give it a try.
> > > > > > > > > >
> > > > > > > > > > Regards
> > > > > > > > > > TK
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ________________________________
> > > > > > > > > > From: zeeschuim atmolgers@
> > > > > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > > Hi Tom
> > > > > > > > > >
> > > > > > > > > > On the torchmate plasmacutter ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ sitedriverÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ they
> > > > > > explain
> > > > > > > > how the driver for the plasma cutter works.
> > > > > > > > > > They speak about X and Y movements and never about the Z
> > > > > > movement, I
> > > > > > > > think the Z movement is totally ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ out of the cooordinate system.
> > > > > > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > > > > > >
> > > > > > > > > > what do you think?
> > > > > > > > > >
> > > > > > > > > > Cees
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6067 From: bennyattwell Date: 11/13/2012
Subject: Re: torch height control in Mach
i use a c and cnc torch height at the moment on my plasma.
their yahoo forum has many answers to things you wouldnt think cause faults like dives etc and is well worth subscribing to.
http://groups.yahoo.com/group/CandCNCSupport/


it helped me a lot and "tom caudle" really knows his stuff on plasma
it would be well worth reading toms answers to questions over the last month for example as he goes into depth of why things go wrong or dont work .
for example mach3 ignores the acceleration setting when responding to thc up/down movements
i always monitor the support forum for a product im going to purchase, that way i know how much support il get etc.

im amazed how much ive learnt about motion and programming from this forum, mr kerekes you are a very good teacher and product support seems the best ive seen anywhere.

--- In DynoMotion@yahoogroups.com, "zeeschuim" <atmolgers@...> wrote:
>
> I will read it
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Cees,
> >
> > If you found out what those actually do we could do something similar like I described.
> >
> > The obvious problem with setting limits is if for example we start at a height of 5mm and the flatness of your material varies by +/- 10mm then we must allow +/- 10mm of motion so that wouldn't necessarily help crashing.
> >
> > I Google and found this:
> >
> > http://www.cnczone.com/forums/mach_plasma_laser/103229-thc_settings_explanation_-_clear.html
> >
> > And this (ignore THC Up/Down when the xy velocity is slow)
> >
> > http://www.machsupport.com/forum/index.php?topic=16169.0
> >
> > We can do anything you wish but you must understand the problem first.
> >
> > Regards
> > TK
> >
> >
> >
> >
> > ________________________________
> > From: zeeschuim <atmolgers@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, November 13, 2012 1:01 PM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > Hi Tom
> >
> > In the Mach3 plasma screenset, there are two DRO's for the max height and the Min. height.
> > Or something in machine coordinates?
> >
> > regards,
> > Cees
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Cees,
> > >
> > > ok. You might want to have the program to remember the z height when the THC ON first comes on.  Then disallow motion if z ever tries to move too far from that starting position.  But if your panels have a lot of curvature that wouldn't really help.
> > >
> > > I've heard Users mention "anti-dive" methods.  But I don't know what that is exactly. 
> > >
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim <atmolgers@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Tuesday, November 13, 2012 12:44 PM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > >  
> > > ok
> > > sometimes it goes to deep or to hi, it is lost control totally.
> > > But maybe it is the speed.
> > > Now it goes 800mm/min and this is to fast for my THC, I think.
> > > I will change it to 100mm or less.
> > >
> > > regards,
> > > Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Cees,
> > > >
> > > > You could issue a MoveRelAtVel instead of a Jog, but I'm not sure that would make sense.  Don't you want to move until it tells you to stop?
> > > >
> > > > The difference is that it would then stop after some distance if never told to stop.  But would do another move if it commanded a stop and then another move.
> > > >
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim <atmolgers@>
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Tuesday, November 13, 2012 12:02 PM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >
> > > >  
> > > > Ok
> > > > I thought they were the distances.
> > > > Can the distance also be done?
> > > >
> > > > regards,
> > > > Cees
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Cees,
> > > > >
> > > > > Certainly.ÃÆ'‚  Change the Jog Speeds.ÃÆ'‚  (they are the 10000 and -10000 steps per second)
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim atmolgers@
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Tuesday, November 13, 2012 7:48 AM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >
> > > > > ÃÆ'‚ 
> > > > > Hi Tom
> > > > >
> > > > > Is there aÃÆ'‚ possibility to adjust the speed of the Z axe in THC mode?
> > > > > According the PolishÃÆ'‚ manufacturerÃÆ'‚ is it maybe to fast.
> > > > >
> > > > > if (ReadBit(143)) // if plasma is ON?
> > > > > {
> > > > >
> > > > > if (ReadBit(142)) ÃÆ'‚  //Up?
> > > > > {
> > > > > Delay_sec(0.1); // Delay for error filter
> > > > > Jog(2,10000); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  // Axis Z move UP
> > > > > while (ReadBit(142)) ;
> > > > > Jog(2,0); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚ ÃÆ'‚ 
> > > > > while (!CheckDone(2)) ÃÆ'‚ ; ÃÆ'‚ ÃÆ'‚ 
> > > > > }
> > > > > else if (ReadBit(141)) //DOWN?
> > > > > {
> > > > > Delay_sec(0.1); //Delay.
> > > > > Jog(2,-10000); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  // Axis Z move DOWN
> > > > > while (ReadBit(141)) ;
> > > > > Jog(2,0); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚ ÃÆ'‚ 
> > > > > while (!CheckDone(2)) ÃÆ'‚ ; ÃÆ'‚ ÃÆ'‚ 
> > > > > }
> > > > > }
> > > > > }
> > > > > ÃÆ'‚ regards,
> > > > > Cees
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > >
> > > > > > Cees,
> > > > > >
> > > > > > Excellent!ÃÆ'Æ'‚ÃÆ'‚  Are the files you uploaded to your folder the working ones?
> > > > > >
> > > > > > Regards
> > > > > > TK
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: zeeschuim atmolgers@
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Monday, November 12, 2012 8:36 AM
> > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > >
> > > > > >
> > > > > > ÃÆ'Æ'‚ÃÆ'‚ 
> > > > > > Hi Tom
> > > > > >
> > > > > > All the progams are working!
> > > > > > Only I have to tame the Polish THC
> > > > > > It is going like a drunken sailor!
> > > > > >
> > > > > > Thanks for the help!
> > > > > > Cees
> > > > > >
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > > >
> > > > > > > Never try to close an output 10With a macro M14 what is telling to do"
> > > > > > > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > > > > > > regards,Cees
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > > > >
> > > > > > > > I don't know it anymore
> > > > > > > >
> > > > > > > >
> > > > > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > > > > >
> > > > > > > > > Hi Tom
> > > > > > > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > > > > > > close
> > > > > > > > > this pin 48 output, the torch on/of bit can be used?
> > > > > > > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > > > > > > Moves+---------------------------------------------------begin
> > > > > > > > > PLUNGE_MOVE
> > > > > > > > > "M15" // this the G31 macro to measure the top of the material, go
> > > > > > > to
> > > > > > > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > > > > > > 1)
> > > > > > > > > then cutting with THcontrol
> > > > > > > > > torch of bit wil close pin48 and // Plasma is off switch to normal
> > > > > > > Z
> > > > > > > > > mode
> > > > > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > > > > this should be ok, don't you think?
> > > > > > > > > regards,Cees
> > > > > > > > >
> > > > > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Cees,
> > > > > > > > > >
> > > > > > > > > > If I understand you correctly.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Using Torch On to switch modes
> > > > > > > > > will not work, because after the Torch is switched on we still need
> > > > > > > to
> > > > > > > > > move Z to the 1.5mm height from GCode.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ So we need a different
> > > > > > > > > command (or bit) other than Torch On to switch modes.
> > > > > > > > > >
> > > > > > > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > > > > > > change
> > > > > > > > > modes.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ We don't need a real physical bit that we output and
> > > > > > > wire
> > > > > > > > > back into a Kanalog Input Bit.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ We can simply use a KFLOP
> > > > > > > Virtual
> > > > > > > > > Bit.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ These are designed exactly for this type of purpose.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > It
> > > > > > > > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> > > > > > > and
> > > > > > > > > off like a real output bit, but KFLOP can also observe and test like
> > > > > > > an
> > > > > > > > > input.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Let's use Virtual Bit #48.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > > > > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > > > > > > the
> > > > > > > > > Mach3 Macro?
> > > > > > > > > >
> > > > > > > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > > > > > > >
> > > > > > > > > > Let me know how much of this makes sense.
> > > > > > > > > >
> > > > > > > > > > Regards
> > > > > > > > > > TK
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ________________________________
> > > > > > > > > > From: zeeschuim atmolgers@
> > > > > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > > Hi Tom
> > > > > > > > > >
> > > > > > > > > > I will try it tomorrow
> > > > > > > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> > > > > > > the
> > > > > > > > > torch ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ on.
> > > > > > > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > > > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > > > > > > All this can happen in the same G31 macro.
> > > > > > > > > > We use this output for a kanalog input and use it as theÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > > > > >
> > > > > > > > > > make this sense?
> > > > > > > > > > regards,
> > > > > > > > > > Cees
> > > > > > > > > >
> > > > > > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi Cees,
> > > > > > > > > > >
> > > > > > > > > > > I think you are correct.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ The way we are now has the Z axis
> > > > > > > > > being driven both by the GCode Coordinated Motion System and the THC
> > > > > > > > > Jogs.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ This is basically like telling the motor to go to two
> > > > > > > > > different
> > > > > > > > > > > places at the same time.
> > > > > > > > > > >
> > > > > > > > > > > I think we require two modes of operation.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ The Z axis can
> > > > > > > be
> > > > > > > > > added and removed from GCode control with the statements shown
> > > > > > > below:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ // Plasma is on
> > > > > > > > > switch, remove Z from System to allow THC
> > > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ // Plasma is off
> > > > > > > > > switch to normal Z mode
> > > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > It just isn't clear to me what signal we should use to switch
> > > > > > > > > modes.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Let's try using the Torch ON signal coming from the
> > > > > > > > > unit.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Although it isn't totally clear to me what that is.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > Does
> > > > > > > > > that indicate that the arc is turned on?ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Or that the arc is
> > > > > > > > > ready?ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Maybe it would be better to have a separate bit that we
> > > > > > > can
> > > > > > > > > switch independently of all that?ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Anyway let's try using the
> > > > > > > Torch
> > > > > > > > > ON signal.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ I've modified the C program as V4 and uploaded
> > > > > > > it.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > Please give it a try.
> > > > > > > > > > >
> > > > > > > > > > > Regards
> > > > > > > > > > > TK
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > ________________________________
> > > > > > > > > > > From: zeeschuim atmolgers@
> > > > > > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > > > Hi Tom
> > > > > > > > > > >
> > > > > > > > > > > On the torchmate plasmacutter ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ sitedriverÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ they
> > > > > > > explain
> > > > > > > > > how the driver for the plasma cutter works.
> > > > > > > > > > > They speak about X and Y movements and never about the Z
> > > > > > > movement, I
> > > > > > > > > think the Z movement is totally ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ out of the cooordinate system.
> > > > > > > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > > > > > > >
> > > > > > > > > > > what do you think?
> > > > > > > > > > >
> > > > > > > > > > > Cees
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6068 From: Shannon Davenport Date: 11/13/2012
Subject: Re: torch height control in Mach

Hi Cees,
Typically you don't  want any delay in THC control.  1 arc volt = about. 004".  You can build a lot of error in .1 sec.  THC is usually done with some kind of PID control.
Shannon

On Nov 13, 2012 10:49 AM, "zeeschuim" <atmolgers@...> wrote:
 

Hi Tom


Is there a possibility to adjust the speed of the Z axe in THC mode?
According the Polish manufacturer is it maybe to fast.

if (ReadBit(143)) // if plasma is ON?
{

if (ReadBit(142))   //Up?
{
Delay_sec(0.1); // Delay for error filter
Jog(2,10000);           // Axis Z move UP
while (ReadBit(142)) ;
Jog(2,0);       
while (!CheckDone(2))  ;   
}
else if (ReadBit(141)) //DOWN?
{
Delay_sec(0.1); //Delay.
Jog(2,-10000);           // Axis Z move DOWN
while (ReadBit(141)) ;
Jog(2,0);       
while (!CheckDone(2))  ;   
}
}
}
 regards,
Cees
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Cees,
>
> Excellent!  Are the files you uploaded to your folder the working ones?
>
> Regards
> TK
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Monday, November 12, 2012 8:36 AM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> All the progams are working!
> Only I have to tame the Polish THC
> It is going like a drunken sailor!
>
> Thanks for the help!
> Cees
>
>
> --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> >
> > Never try to close an output 10With a macro M14 what is telling to do"
> > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > regards,Cees
> >
> > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > >
> > > I don't know it anymore
> > >
> > >
> > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > >
> > > > Hi Tom
> > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > close
> > > > this pin 48 output, the torch on/of bit can be used?
> > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > Moves+---------------------------------------------------begin
> > > > PLUNGE_MOVE
> > > > "M15" // this the G31 macro to measure the top of the material, go
> > to
> > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > 1)
> > > > then cutting with THcontrol
> > > > torch of bit wil close pin48 and // Plasma is off switch to normal
> > Z
> > > > mode
> > > > DefineCoordSystem(0,1,2,-1);
> > > > this should be ok, don't you think?
> > > > regards,Cees
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > Hi Cees,
> > > > >
> > > > > If I understand you correctly. Using Torch On to switch modes
> > > > will not work, because after the Torch is switched on we still need
> > to
> > > > move Z to the 1.5mm height from GCode. So we need a different
> > > > command (or bit) other than Torch On to switch modes.
> > > > >
> > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > change
> > > > modes. We don't need a real physical bit that we output and
> > wire
> > > > back into a Kanalog Input Bit. We can simply use a KFLOP
> > Virtual
> > > > Bit. These are designed exactly for this type of purpose.Â
> > It
> > > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> > and
> > > > off like a real output bit, but KFLOP can also observe and test like
> > an
> > > > input. Let's use Virtual Bit #48.Â
> > > > >
> > > > >
> > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > the
> > > > Mach3 Macro?
> > > > >
> > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > >
> > > > > Let me know how much of this makes sense.
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim atmolgers@
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >
> > > > > Â
> > > > > Hi Tom
> > > > >
> > > > > I will try it tomorrow
> > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> > the
> > > > torch  on.
> > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > All this can happen in the same G31 macro.
> > > > > We use this output for a kanalog input and use it as the Â
> > Â
> > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > Â Â Â Â Â Â Â
> > DefineCoordSystem(0,1,-1,-1);
> > > > >
> > > > > make this sense?
> > > > > regards,
> > > > > Cees
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > >
> > > > > > Hi Cees,
> > > > > >
> > > > > > I think you are correct. The way we are now has the Z axis
> > > > being driven both by the GCode Coordinated Motion System and the THC
> > > > Jogs. This is basically like telling the motor to go to two
> > > > different
> > > > > > places at the same time.
> > > > > >
> > > > > > I think we require two modes of operation. The Z axis can
> > be
> > > > added and removed from GCode control with the statements shown
> > below:
> > > > > >
> > > > > >
> > > > > > Â Â Â Â Â Â Â Â Â // Plasma is on
> > > > switch, remove Z from System to allow THC
> > > > > > Â Â Â Â Â Â Â Â Â
> > > > DefineCoordSystem(0,1,-1,-1);
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Â Â Â Â Â Â Â Â Â // Plasma is off
> > > > switch to normal Z mode
> > > > > > Â Â Â Â Â Â Â Â Â
> > > > DefineCoordSystem(0,1,2,-1);
> > > > > >
> > > > > >
> > > > > >
> > > > > > It just isn't clear to me what signal we should use to switch
> > > > modes. Let's try using the Torch ON signal coming from the
> > > > unit. Although it isn't totally clear to me what that is.Â
> > Does
> > > > that indicate that the arc is turned on? Or that the arc is
> > > > ready? Maybe it would be better to have a separate bit that we
> > can
> > > > switch independently of all that? Anyway let's try using the
> > Torch
> > > > ON signal. I've modified the C program as V4 and uploaded
> > it.Â
> > > > Please give it a try.
> > > > > >
> > > > > > Regards
> > > > > > TK
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: zeeschuim atmolgers@
> > > > > > To: DynoMotion@yahoogroups.com
> > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > >
> > > > > >
> > > > > > Â
> > > > > > Hi Tom
> > > > > >
> > > > > > On the torchmate plasmacutter  sitedriver  they
> > explain
> > > > how the driver for the plasma cutter works.
> > > > > > They speak about X and Y movements and never about the Z
> > movement, I
> > > > think the Z movement is totally  out of the cooordinate system.
> > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > >
> > > > > > what do you think?
> > > > > >
> > > > > > Cees
> > > > > >
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6073 From: zeeschuim Date: 11/13/2012
Subject: Re: torch height control in Mach
Hi Shannon

I will remove it,
thanks,
Cees

--- In DynoMotion@yahoogroups.com, Shannon Davenport <sdavenport.roa@...> wrote:
>
> Hi Cees,
> Typically you don't want any delay in THC control. 1 arc volt = about.
> 004". You can build a lot of error in .1 sec. THC is usually done with
> some kind of PID control.
> Shannon
> On Nov 13, 2012 10:49 AM, "zeeschuim" <atmolgers@...> wrote:
>
> > **
> >
> >
> > Hi Tom
> >
> > Is there a p*ossibility to adjust the speed of the Z axe in THC mode?*
> > *According the Polish **manufacturer** is it maybe to fast.*
> >
> > if (ReadBit(143)) // if plasma is ON?
> > {
> >
> > if (ReadBit(142)) //Up?
> > {
> > Delay_sec(0.1); // Delay for error filter
> > Jog(2,10000); // Axis Z move UP
> > while (ReadBit(142)) ;
> > Jog(2,0);
> > while (!CheckDone(2)) ;
> > }
> > else if (ReadBit(141)) //DOWN?
> > {
> > Delay_sec(0.1); //Delay.
> > Jog(2,-10000); // Axis Z move DOWN
> > while (ReadBit(141)) ;
> > Jog(2,0);
> > while (!CheckDone(2)) ;
> > }
> > }
> > }
> > regards,
> > Cees
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Cees,
> > >
> > > Excellent! Are the files you uploaded to your folder the working ones?
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim atmolgers@
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Monday, November 12, 2012 8:36 AM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > > Â
> > > Hi Tom
> > >
> > > All the progams are working!
> > > Only I have to tame the Polish THC
> > > It is going like a drunken sailor!
> > >
> > > Thanks for the help!
> > > Cees
> > >
> > >
> > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > >
> > > > Never try to close an output 10With a macro M14 what is telling to do"
> > > > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > > > regards,Cees
> > > >
> > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > >
> > > > > I don't know it anymore
> > > > >
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > >
> > > > > > Hi Tom
> > > > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > > > close
> > > > > > this pin 48 output, the torch on/of bit can be used?
> > > > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > > > Moves+---------------------------------------------------begin
> > > > > > PLUNGE_MOVE
> > > > > > "M15" // this the G31 macro to measure the top of the material, go
> > > > to
> > > > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > > > 1)
> > > > > > then cutting with THcontrol
> > > > > > torch of bit wil close pin48 and // Plasma is off switch to normal
> > > > Z
> > > > > > mode
> > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > this should be ok, don't you think?
> > > > > > regards,Cees
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > >
> > > > > > > Hi Cees,
> > > > > > >
> > > > > > > If I understand you correctly. Using Torch On to switch modes
> > > > > > will not work, because after the Torch is switched on we still need
> > > > to
> > > > > > move Z to the 1.5mm height from GCode. So we need a different
> > > > > > command (or bit) other than Torch On to switch modes.
> > > > > > >
> > > > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > > > change
> > > > > > modes. We don't need a real physical bit that we output and
> > > > wire
> > > > > > back into a Kanalog Input Bit. We can simply use a KFLOP
> > > > Virtual
> > > > > > Bit. These are designed exactly for this type of purpose.Â
> > > > It
> > > > > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> > > > and
> > > > > > off like a real output bit, but KFLOP can also observe and test
> > like
> > > > an
> > > > > > input. Let's use Virtual Bit #48.Â
> > > > > > >
> > > > > > >
> > > > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > > > the
> > > > > > Mach3 Macro?
> > > > > > >
> > > > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > > > >
> > > > > > > Let me know how much of this makes sense.
> > > > > > >
> > > > > > > Regards
> > > > > > > TK
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: zeeschuim atmolgers@
> > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > >
> > > > > > >
> > > > > > > Â
> > > > > > > Hi Tom
> > > > > > >
> > > > > > > I will try it tomorrow
> > > > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> > > > the
> > > > > > torch  on.
> > > > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > > > All this can happen in the same G31 macro.
> > > > > > > We use this output for a kanalog input and use it as the Â
> > > > Â
> > > > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > > > Â Â Â Â Â Â Â
> > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > >
> > > > > > > make this sense?
> > > > > > > regards,
> > > > > > > Cees
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > > > >
> > > > > > > > Hi Cees,
> > > > > > > >
> > > > > > > > I think you are correct. The way we are now has the Z axis
> > > > > > being driven both by the GCode Coordinated Motion System and the
> > THC
> > > > > > Jogs. This is basically like telling the motor to go to two
> > > > > > different
> > > > > > > > places at the same time.
> > > > > > > >
> > > > > > > > I think we require two modes of operation. The Z axis can
> > > > be
> > > > > > added and removed from GCode control with the statements shown
> > > > below:
> > > > > > > >
> > > > > > > >
> > > > > > > > Â Â Â Â Â Â Â Â Â // Plasma is on
> > > > > > switch, remove Z from System to allow THC
> > > > > > > > Â Â Â Â Â Â Â Â Â
> > > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Â Â Â Â Â Â Â Â Â // Plasma is off
> > > > > > switch to normal Z mode
> > > > > > > > Â Â Â Â Â Â Â Â Â
> > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > It just isn't clear to me what signal we should use to switch
> > > > > > modes. Let's try using the Torch ON signal coming from the
> > > > > > unit. Although it isn't totally clear to me what that is.Â
> > > > Does
> > > > > > that indicate that the arc is turned on? Or that the arc is
> > > > > > ready? Maybe it would be better to have a separate bit that we
> > > > can
> > > > > > switch independently of all that? Anyway let's try using the
> > > > Torch
> > > > > > ON signal. I've modified the C program as V4 and uploaded
> > > > it.Â
> > > > > > Please give it a try.
> > > > > > > >
> > > > > > > > Regards
> > > > > > > > TK
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ________________________________
> > > > > > > > From: zeeschuim atmolgers@
> > > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > >
> > > > > > > >
> > > > > > > > Â
> > > > > > > > Hi Tom
> > > > > > > >
> > > > > > > > On the torchmate plasmacutter  sitedriver  they
> > > > explain
> > > > > > how the driver for the plasma cutter works.
> > > > > > > > They speak about X and Y movements and never about the Z
> > > > movement, I
> > > > > > think the Z movement is totally  out of the cooordinate system.
> > > > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > > > >
> > > > > > > > what do you think?
> > > > > > > >
> > > > > > > > Cees
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
>
Group: DynoMotion Message: 6074 From: zeeschuim Date: 11/14/2012
Subject: Re: torch height control in Mach
Hi Tom

It works!
The THC speed is now 125 mm/min, no delay  and it is working fine

Thanks for your patience and all the help!:)
 regards,
Cees


--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Cees,
>
> If you found out what those actually do we could do something similar like I described.
>
> The obvious problem with setting limits is if for example we start at a height of 5mm and the flatness of your material varies by +/- 10mm then we must allow +/- 10mm of motion so that wouldn't necessarily help crashing.
>
> I Google and found this:
>
> http://www.cnczone.com/forums/mach_plasma_laser/103229-thc_settings_explanation_-_clear.html
>
> And this (ignore THC Up/Down when the xy velocity is slow)
>
> http://www.machsupport.com/forum/index.php?topic=16169.0
>
> We can do anything you wish but you must understand the problem first.
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: zeeschuim atmolgers@...
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, November 13, 2012 1:01 PM
> Subject: [DynoMotion] Re: torch height control in Mach
>
>
>  
> Hi Tom
>
> In the Mach3 plasma screenset, there are two DRO's for the max height and the Min. height.
> Or something in machine coordinates?
>
> regards,
> Cees
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> >
> > Hi Cees,
> >
> > ok. You might want to have the program to remember the z height when the THC ON first comes on.  Then disallow motion if z ever tries to move too far from that starting position.  But if your panels have a lot of curvature that wouldn't really help.
> >
> > I've heard Users mention "anti-dive" methods.  But I don't know what that is exactly. 
> >
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: zeeschuim atmolgers@
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, November 13, 2012 12:44 PM
> > Subject: [DynoMotion] Re: torch height control in Mach
> >
> >
> >  
> > ok
> > sometimes it goes to deep or to hi, it is lost control totally.
> > But maybe it is the speed.
> > Now it goes 800mm/min and this is to fast for my THC, I think.
> > I will change it to 100mm or less.
> >
> > regards,
> > Cees
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Cees,
> > >
> > > You could issue a MoveRelAtVel instead of a Jog, but I'm not sure that would make sense.  Don't you want to move until it tells you to stop?
> > >
> > > The difference is that it would then stop after some distance if never told to stop.  But would do another move if it commanded a stop and then another move.
> > >
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: zeeschuim <atmolgers@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Tuesday, November 13, 2012 12:02 PM
> > > Subject: [DynoMotion] Re: torch height control in Mach
> > >
> > >
> > >  
> > > Ok
> > > I thought they were the distances.
> > > Can the distance also be done?
> > >
> > > regards,
> > > Cees
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Cees,
> > > >
> > > > Certainly.ÃÆ'‚  Change the Jog Speeds.ÃÆ'‚  (they are the 10000 and -10000 steps per second)
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: zeeschuim atmolgers@
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Tuesday, November 13, 2012 7:48 AM
> > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > >
> > > >
> > > > ÃÆ'‚ 
> > > > Hi Tom
> > > >
> > > > Is there aÃÆ'‚ possibility to adjust the speed of the Z axe in THC mode?
> > > > According the PolishÃÆ'‚ manufacturerÃÆ'‚ is it maybe to fast.
> > > >
> > > > if (ReadBit(143)) // if plasma is ON?
> > > > {
> > > >
> > > > if (ReadBit(142)) ÃÆ'‚  //Up?
> > > > {
> > > > Delay_sec(0.1); // Delay for error filter
> > > > Jog(2,10000); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  // Axis Z move UP
> > > > while (ReadBit(142)) ;
> > > > Jog(2,0); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚ ÃÆ'‚ 
> > > > while (!CheckDone(2)) ÃÆ'‚ ; ÃÆ'‚ ÃÆ'‚ 
> > > > }
> > > > else if (ReadBit(141)) //DOWN?
> > > > {
> > > > Delay_sec(0.1); //Delay.
> > > > Jog(2,-10000); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  ÃÆ'‚  // Axis Z move DOWN
> > > > while (ReadBit(141)) ;
> > > > Jog(2,0); ÃÆ'‚  ÃÆ'‚  ÃÆ'‚ ÃÆ'‚ 
> > > > while (!CheckDone(2)) ÃÆ'‚ ; ÃÆ'‚ ÃÆ'‚ 
> > > > }
> > > > }
> > > > }
> > > > ÃÆ'‚ regards,
> > > > Cees
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > >
> > > > > Cees,
> > > > >
> > > > > Excellent!ÃÆ'Æ'‚ÃÆ'‚  Are the files you uploaded to your folder the working ones?
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: zeeschuim atmolgers@
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Monday, November 12, 2012 8:36 AM
> > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > >
> > > > >
> > > > > ÃÆ'Æ'‚ÃÆ'‚ 
> > > > > Hi Tom
> > > > >
> > > > > All the progams are working!
> > > > > Only I have to tame the Polish THC
> > > > > It is going like a drunken sailor!
> > > > >
> > > > > Thanks for the help!
> > > > > Cees
> > > > >
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > >
> > > > > > Never try to close an output 10With a macro M14 what is telling to do"
> > > > > > DeActivateSignal(Output4)"It is NOT!! going to work! [#-o]
> > > > > > regards,Cees
> > > > > >
> > > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > > >
> > > > > > > I don't know it anymore
> > > > > > >
> > > > > > >
> > > > > > > --- In DynoMotion@yahoogroups.com, "zeeschuim" atmolgers@ wrote:
> > > > > > > >
> > > > > > > > Hi Tom
> > > > > > > > Yes I think I can do that.It is pin 48 on port 1? am I right?To
> > > > > > close
> > > > > > > > this pin 48 output, the torch on/of bit can be used?
> > > > > > > > In the postprocessor it will be:+ Commands output for Plunge
> > > > > > > > Moves+---------------------------------------------------begin
> > > > > > > > PLUNGE_MOVE
> > > > > > > > "M15" // this the G31 macro to measure the top of the material, go
> > > > > > to
> > > > > > > > pierceheight, torch on, go to cutheight, do output 3 ( pin48 port
> > > > > > 1)
> > > > > > > > then cutting with THcontrol
> > > > > > > > torch of bit wil close pin48 and // Plasma is off switch to normal
> > > > > > Z
> > > > > > > > mode
> > > > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > > > this should be ok, don't you think?
> > > > > > > > regards,Cees
> > > > > > > >
> > > > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > > > > > >
> > > > > > > > > Hi Cees,
> > > > > > > > >
> > > > > > > > > If I understand you correctly.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Using Torch On to switch modes
> > > > > > > > will not work, because after the Torch is switched on we still need
> > > > > > to
> > > > > > > > move Z to the 1.5mm height from GCode.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ So we need a different
> > > > > > > > command (or bit) other than Torch On to switch modes.
> > > > > > > > >
> > > > > > > > > OK let's use an output "bit" that Mach3 can turn on and off to
> > > > > > change
> > > > > > > > modes.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ We don't need a real physical bit that we output and
> > > > > > wire
> > > > > > > > back into a Kanalog Input Bit.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ We can simply use a KFLOP
> > > > > > Virtual
> > > > > > > > Bit.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ These are designed exactly for this type of purpose.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > It
> > > > > > > > is like a flag that exists only inside KFLOP that Mach3 can turn on
> > > > > > and
> > > > > > > > off like a real output bit, but KFLOP can also observe and test like
> > > > > > an
> > > > > > > > input.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Let's use Virtual Bit #48.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Do you know how to configure an output bit in the Mach3 Config |
> > > > > > > > Ports&Pins | Outputs for Pin 48 Port 1 and turn it off and on from
> > > > > > the
> > > > > > > > Mach3 Macro?
> > > > > > > > >
> > > > > > > > > I've uploaded a V5 that uses bit48 to change modes.
> > > > > > > > >
> > > > > > > > > Let me know how much of this makes sense.
> > > > > > > > >
> > > > > > > > > Regards
> > > > > > > > > TK
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ________________________________
> > > > > > > > > From: zeeschuim atmolgers@
> > > > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > > > Sent: Saturday, November 10, 2012 10:35 AM
> > > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > Hi Tom
> > > > > > > > >
> > > > > > > > > I will try it tomorrow
> > > > > > > > > At the G31 macro the Z axe goes to pierceheight, 5mm, then switch
> > > > > > the
> > > > > > > > torch ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ on.
> > > > > > > > > After the torch is on the Z axe will go to 1.5mm cutheight.
> > > > > > > > > At cutheight 1.5mm we can Mach3 do an output.
> > > > > > > > > All this can happen in the same G31 macro.
> > > > > > > > > We use this output for a kanalog input and use it as theÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > // Plasma is on switch, remove Z from System to allow THC
> > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > > > >
> > > > > > > > > make this sense?
> > > > > > > > > regards,
> > > > > > > > > Cees
> > > > > > > > >
> > > > > > > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes tk@ wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Cees,
> > > > > > > > > >
> > > > > > > > > > I think you are correct.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ The way we are now has the Z axis
> > > > > > > > being driven both by the GCode Coordinated Motion System and the THC
> > > > > > > > Jogs.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ This is basically like telling the motor to go to two
> > > > > > > > different
> > > > > > > > > > places at the same time.
> > > > > > > > > >
> > > > > > > > > > I think we require two modes of operation.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ The Z axis can
> > > > > > be
> > > > > > > > added and removed from GCode control with the statements shown
> > > > > > below:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ // Plasma is on
> > > > > > > > switch, remove Z from System to allow THC
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > DefineCoordSystem(0,1,-1,-1);
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ // Plasma is off
> > > > > > > > switch to normal Z mode
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > DefineCoordSystem(0,1,2,-1);
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > It just isn't clear to me what signal we should use to switch
> > > > > > > > modes.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Let's try using the Torch ON signal coming from the
> > > > > > > > unit.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Although it isn't totally clear to me what that is.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > Does
> > > > > > > > that indicate that the arc is turned on?ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Or that the arc is
> > > > > > > > ready?ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Maybe it would be better to have a separate bit that we
> > > > > > can
> > > > > > > > switch independently of all that?ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ Anyway let's try using the
> > > > > > Torch
> > > > > > > > ON signal.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ I've modified the C program as V4 and uploaded
> > > > > > it.ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > Please give it a try.
> > > > > > > > > >
> > > > > > > > > > Regards
> > > > > > > > > > TK
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ________________________________
> > > > > > > > > > From: zeeschuim atmolgers@
> > > > > > > > > > To: DynoMotion@yahoogroups.com
> > > > > > > > > > Sent: Saturday, November 10, 2012 7:50 AM
> > > > > > > > > > Subject: [DynoMotion] Re: torch height control in Mach
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡
> > > > > > > > > > Hi Tom
> > > > > > > > > >
> > > > > > > > > > On the torchmate plasmacutter ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ sitedriverÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ they
> > > > > > explain
> > > > > > > > how the driver for the plasma cutter works.
> > > > > > > > > > They speak about X and Y movements and never about the Z
> > > > > > movement, I
> > > > > > > > think the Z movement is totally ÃÆ'Æ'Æ'ÃÆ'¢â‚¬Å¡ out of the cooordinate system.
> > > > > > > > > > I think it is moved by the G31 macro and then by the THC.
> > > > > > > > > >
> > > > > > > > > > what do you think?
> > > > > > > > > >
> > > > > > > > > > Cees
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>